yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] wiitwd:
I have the same problem on my i605. I've done factory reset, wiped everything, flashed the latest nightly (cm-12.1-20150511-NIGHTLY-flo.zip) and pa_gapps-stock-5.1-20150418-signed.zip to no avail.

Incoming calls still ring several times and then go to voicejail. Another anomaly is that outgoing calls don't want to hang up. Calling my bank's voice menu system or leaving a voice mail requires me to power-off or reboot the phone to terminate the call. Calls will end if the other end hangs up.

I've reverted to cm-12-20150130-NIGHTLY-i605.zip via a ROM copy found on AndroidHost at which does have a working phone section. I can't post a link as yet, but searching for "cm-12-20150130-NIGHTLY-i605.zip" will lead you to it.
[Verizon Samsung Galaxy Note II] jobren:
Temporary solution

According to beddess in the official cm12.1 thread

http://xdaforums.com/showpost.php?p=60829301&postcount=513

t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list

Like this

getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||

Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.
[Verizon Samsung Galaxy Note II] wiitwd:
Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.
[Verizon Samsung Galaxy Note II] jobren:
Any good news? I noticed lots of updates going on in the nughtlies. I myself didn't get much luck with the nightly one week before.
[Verizon Samsung Galaxy Note II] wiitwd:
As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.
[Verizon Samsung Galaxy Note II] harjotsandhu:
I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9
[Verizon Samsung Galaxy Note II] harjotsandhu:
I tried the given method with 13 July 2015 nightly and it works. Saved my life. I upgraded my MJ9 baseband to ND7 with no effect. Only the given around is working.
[Verizon Samsung Galaxy Note II] RJ803:
I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated

RJ
[Verizon Samsung Galaxy Note II] wiitwd:
I have some new information. When using the i605 nightlies, telephony fails to hang up calls or to receive incoming calls while in a GSM service area, e.g., Guam. Now that I'm back stateside in CDMA/LTE land, the i605 nightlies work great. I offer as a working hypothesis, therefore, that GSM telephony is broken in the i605 nightlies. When I go back in October I'll bring the latest modified t0lte nightly as well as my GTA SIM card.
[Verizon Samsung Galaxy Note II] jobren:
I have not tried with other ROMs. It definitly works.

Might worth it to have a look at the file in I605 and check the difference.

Sorry I couldnt upload my file. It seems that I do not have the rights to upload files yet. :silly:
[Verizon Samsung Galaxy Note II] dmcgregor:
I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.

I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.
[Verizon Samsung Galaxy Note II] dmcgregor:
Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option. :)
[Verizon Samsung Galaxy Note II] jobren:
OK. Let's try this.

The following is the content of my script file. Copy it into a empty txt file and rename it as 'updater-script'.....Here we go.

assert(getprop("ro.product.device") == "t0lte" || getprop("ro.build.product") == "t0lte" || getprop("ro.product.device") == "t0ltexx" || getprop("ro.build.product") == "t0ltexx" || getprop("ro.product.device") == "GT-N7105" || getprop("ro.build.product") == "GT-N7105" || getprop("ro.product.device") == "t0ltedv" || getprop("ro.build.product") == "t0ltedv" || getprop("ro.product.device") == "GT-N7105T" || getprop("ro.build.product") == "GT-N7105T" || getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || getprop("ro.product.device") == "SGH-I317" || getprop("ro.build.product") == "SGH-I317" || getprop("ro.product.device") == "t0ltetmo" || getprop("ro.build.product") == "t0ltetmo" || getprop("ro.product.device") == "SGH-T889" || getprop("ro.build.product") == "SGH-T889" || getprop("ro.product.device") == "t0ltecan" || getprop("ro.build.product") == "t0ltecan" || getprop("ro.product.device") == "t0ltevl" || getprop("ro.build.product") == "t0ltevl" || getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M" ||getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || abort("This package is for device: t0lte,t0ltexx,GT-N7105,t0ltedv,GT-N7105T,t0lteatt,SGH-I317,t0ltetmo,SGH-T889,t0ltecan,t0ltevl,SGH-I317M; this device is " + getprop("ro.product.device") + "."););

ifelse(is_mounted("/system"), unmount("/system"));

package_extract_dir("install", "/tmp/install");

set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);

set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);

mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");

run_program("/tmp/install/bin/backuptool.sh", "backup");

unmount("/system");

if is_mounted("/data") then

run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

else

mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/USERDATA", "/data", "");

run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

unmount("/data");

endif;

show_progress(0.750000, 0);

ui_print("Patching system image unconditionally...");

block_image_update("/dev/block/platform/dw_mmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

show_progress(0.020000, 10);

mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");

run_program("/tmp/install/bin/backuptool.sh", "restore");

unmount("/system");

show_progress(0.050000, 5);

package_extract_file("boot.img", "/dev/block/platform/dw_mmc/by-name/BOOT");

show_progress(0.200000, 10);
[Verizon Samsung Galaxy Note II] dmcgregor:
A belated thanks as I'm just now seeing this. After struggling to get this to work for a few weeks I ended up rolling back to CM 11. But I'll give another try with CM 12.1 today and let you know how it goes. Either way I greatly appreciate you taking the time to post this.
[Verizon Samsung Galaxy Note II] dmcgregor:
No dice. Copied the text above into notepad. Saved it over the original updater script. Zipped everything back up and tried to flash, but it failed right away on "updating partition details." No clue what I'm doing wrong. Could it be my recovery? I'm using TWRP 2.8.1.0, which seems to work fine for flashing the i605 version.
[Verizon Samsung Galaxy Note II] jobren:
Emmm…i really don't know now. I have been using this file for several months without any issue. I dont think it is the recovery, either…Could be some details in the formating of the script…or our phones are actually different…

BTW…how many posts it needs to unlock the attachments feature? :p
[Verizon Samsung Galaxy Note II] goofwear:
With the rom zip on your phone download and use ES file explorer. Locate your zip long press it then click the more button. then click extract and press ok. Navigate to the the META-INF\com\google\android\ folder and then long press on the file updater-script and then click rename and then ad .txt to the end so the file is now called updater-script.txt then click ok.

then click on updater-script.txt and open with es file editor. click the pencil in the top right corner to edit text. Then select the text I have shown here

assert(getprop("ro.product.device") == "epic4gtouch" ||
getprop("ro.build.product") == "epic4gtouch" ||
getprop("ro.product.device") == "SPH-D710" ||
getprop("ro.build.product") == "SPH-D710" ||
getprop("ro.product.device") == "d710" ||
getprop("ro.build.product") == "d710" ||
getprop("ro.product.device") == "smdk4210" ||
getprop("ro.build.product") == "smdk4210" ||
getprop("ro.product.device") == "SPH-D710VMUB" ||
getprop("ro.build.product") == "SPH-D710VMUB" ||
getprop("ro.product.device") == "SPH-D710BST" ||
getprop("ro.build.product") == "SPH-D710BST" ||
abort("This package is for device: epic4gtouch,SPH-D710,d710,smdk4210,SPH-D710VMUB,SPH-D710BST; this device is " + getprop("ro.product.device") + "."););

you want to sop at the ) + "."););

and right before the ifelse mount statement. delete the code above.

then press your back button once and then click save.

Then RENAME

updater-script.txt back to updater-script. press your back button a couple of time till you get back to the folder that has all the extracted files and then LONG PRESS and select all the files once they are highlighted then pres the bottom that says more and then click compress. then you can a -modded to the end of the file so you can tell them apart.

after it is done compressing you can delete the other files and keep your new zip.

after you get the hang of this you can do it in under 30 seconds, not including the time to extract and compress the rom.

WARNING THE ASSERT CHECK IS THERE SO YOU CAN NOT ACCIDENTALLY FLASH THIS TO THE WRONG PHONE AND PERMA BRICK YOUR DEVICE.

DELETING THE ASSERT TEXT WILL ALLOW YOU TO FLASH THE NEWLY MODDED ZIP

---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------

Stay off TWRP and philz cutom recovery I have never had a successfully boot, zips would fail halfway through flashing other phone would boot loop. this is back when i was flasinh I605 custom roms of 4.x.x and even cm 11.

I'm on cm 12.1 t0lte Nightly's now and I am using the actual Version I605 Clockword mode recovery with no problems. https://download.cyanogenmod.org/get/jenkins/139629/cm-12.1-20151217-NIGHTLY-i605-recovery.img
[Verizon Samsung Galaxy Note II] Droid_Nut:
I just installed the latest nightly 12-22-15 and made a couple of calls and it rang every time, I am using VZW, so is this not a problem with this carrier, or will it eventually stop working?
[Verizon Samsung Galaxy Note II] Droid_Nut:
Update, I did end up losing only data, so thinking back what could have caused it, the last thing I did was install SuperSu, but removing that did not fix it, I ended up removing Xposed, and that is what fixed it for me. :victory:
[Verizon Samsung Galaxy Note II] Droid_Nut:
Also I would like to note I am using this 5.1.1 Rom. Everything works but face unlock.
[Verizon Samsung Galaxy Note II] Telemachus:
I have been running CM12 for a while now on Verizon Note II. Tried a GSM Sim card and sure enough no incoming calls and unable to hang up. I tried newest nightlies and still no dice.

I tried modifying the other rom mentioned here but install fails with TWRP. I think TWRP is probably the culprit here.

Edit: installed CWM and still no luck. It says the zip file is bad. Could someone PM me with a link to a zip file of a nightly ROM they know works please?
[Samsung Galaxy S II Plus] cracker12:
Hi everyone,

Here i left cm12s gallery and camera app

I leave here the apps because i needed a camera app with pause on video recording for lollipop and this have...

Install like a normal apk

tested on rr v5.4.1, pacman, aosp and cm12
[Samsung Galaxy S II Plus] Raven_Yen:
Does this has stutter lag issue for camera?
[Samsung Galaxy S II Plus] cracker12:
i think so because take almost the same time to take the photo. I only share it because untill now is the only way to have pause on camcorder on lollipop roms
[Samsung Galaxy S II Plus] galfit:
Panorama mode getting FC :(
[Galaxy Note 4 Q&A, Help & Troubleshooting] fredphoesh:
Hi

I have had a Note 4 for months, and have only started having random reboots a week ago.

I have flashed 3 roms since then with full factory / data / cache wipes, and the problem persists.

Other people have had this problem with Stock KK roms.

I think it'd be useful to find out what are the most common scenarios,

KK Lollipop Stock Custom or some app or other issue that you think is suspect, so fill in the poll and comment.

Personally, the problems started around the time I was playing with lock screen replacements... My Locker pro... but it is now uninstalled and I am still getting the reboots 3-8 times a day. I am baffled...

Mark.
[Galaxy Note 4 Q&A, Help & Troubleshooting] xdm9mm:
It would also help to ask what version of Note 4 they have.

On the Note 2, there was also a random reboot problem and it was associated with Sudden Death Syndrome (SDS). Mine was one of them.... I hope this is not a symptom of SDS
[Galaxy Note 4 Q&A, Help & Troubleshooting] fredphoesh:
Last night I flashed

[ROM][N910F][ALEXNDR] ★ BOC3 ★ DevBase, Multi CSC, Safe De-Bloat

and so far so good... no random reboots.

First I flashed the ROM, then I flashed the Kernel, Modem and Bootloader which are also linked to on that ALEXANDR thread. I don't know if this made a difference, but it takes a few seconds, so do it if you are desperate.

After booting up, I restored all my apps, as usual, with titanium backup.

Holding thumbs...
[MDA II, XDA II, 2060 ROM Development] setter:
Hi

I have an XDA 11 which I love and have upgraded it with 2003 se etc from this site

THEN I loved it so much I bought a second XDA11 on Ebay (stop laughing) and it wasnt working so I charged a spare battery and sometimes it boots but mostly just freezes at the inital screen and doesnt even backlight? (Sometimes it does ) It says ROM 1.0.0

Help I would love to get this sucker running for my wife?

Kind regards

John Parker
[MDA II, XDA II, 2060 ROM Development] rocky marsiano:
Hi

try to hard reset it 4 or 5 times if you did it and it didn't work then you have to reflash this device and between me and you give this hima the windows 5.0 it's astonishing in the himalaya , try any of ilbasha ROMS from www.buzzdev.net it's a scream.

amriprahim@hotmail.com
[T-Mobile Samsung Galaxy Note II] BramaKnox:
My Galaxy Note 2 is stuck at the Start up screen screen. Where its an all black bg and simply says Samsung Galaxy Note II

I have tried using recovery mode, cleared cache, and reset to factory. Neither troubleshoot method worked.

I have tried numerous Odin autoroots. none work. Whenever I try to root it fails. Im guessing it might be because I dont have Dev Debug enable and I cant get into my phone to enable it. because of this issue

I have tried looking for TWRP .tar but every file I download the file is always a .img

The Model of the phone is a SGH-T889 (T-mobile Note II)

I am all out of ideas, and I dont know what to do. I have been search for answers for hours and everytime I think I found a solution it doesnt work.
[T-Mobile Samsung Galaxy Note II] ciphercodes:
What ROM was your phone on when this happened ?

Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
[T-Mobile Samsung Galaxy Note II] BramaKnox:
It was on the offical default rom. the phone was never modded, or rooted.

My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.

I can get the phone into download mode, and recovery mode.

In reovery mode I have 6 options

reboot system now

apply update from ADB

apply update from external storage

wipe data/factory reset

wipe cashe partition

apply update from cache

I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.

So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.

I tried using what I believe to be stock frimware files with Odin. and those also Failed.

Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.

I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
[T-Mobile Samsung Galaxy Note II] ciphercodes:
Lets see if we can get this resolved.

1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?

2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).

3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.

4) If your phone was on 4.3 then download this most up to date firmware - from here http://www.sammobile.com/firmwares/download/22863/T889UVUCMK7_T889TMBCMK7_TMB/

5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.

6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.

7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".

8) You can leave Auto reboot and F-reset time checked.

9) Now click Start and let the process finish.

10) If everything goes fine you should see a green message "Pass"

Let me know how it goes.
[T-Mobile Samsung Galaxy Note II] koyanishi:
I have the same problem as the OP (boots only up to Samsung logo with black bg) but it was not caused by niece downloading games but instead from trying to install jedi masterx2 rom.

I did what ciphercodes recommended and put phone in download mode and odin went through the motions of installing the stock os (in my case version 4.3) but after apparently installing the rom it again booted up to Samsung note II logo in black bg.

luckily I can install either Clockword mod recovery v6.0.4.3 or teamwin v2.8.6.0

The clockword mod recovery can read the external sd card (whereas funnily enough the teamwin can't) and I can attempt recovery from previous backups on cmr or to install a rom from zip file but neither of these work - reboots again to Samsung logo in black background after apparently installing the rom.

both teamwin and cwr mention that they can't mount system and that's probably why no rom is install either using cwr or odin so my guess is that I have to reformat the partitions cause probably efs file is corrupt but I don't know how to do that and I have done extensive search in google but have not found a solution

so ciphercodes if you or anyone reading this can help please reply to this message
[T-Mobile Samsung Galaxy Note II] BramaKnox:
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.

I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
[T-Mobile Samsung Galaxy Note II] koyanishi:
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3

When you go to download mode do you see "custom binary download: yes ..."

and do you see "knox warranty void:" ?

if so, your phone has been rooted.

but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
[T-Mobile Samsung Galaxy Note II] BramaKnox:
No it says

Product Name: SGH-T889

Custom Binary Download: No

Current Binary: Samsung Official

System Status: Official

Knox Warranty Void: 0

RP SWAEV: A2
[T-Mobile Samsung Galaxy Note II] koyanishi:
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
[T-Mobile Samsung Galaxy Note II] BramaKnox:
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
[T-Mobile Samsung Galaxy Note II] koyanishi:
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.

Probably you should try to root your phone using instructions from this thread

http://xdaforums.com/showthread.php?t=2562994

But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
[T-Mobile Samsung Galaxy Note II] BramaKnox:
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do