yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] invertedskull:
Stuck in Recovery (TWRP) boot loop!

Hi. I've got a strange problem with my Galaxy Note 2 (GT-N7015). I've searched for similar issues, but only one slightly similar result was found. I need more specific help, so I hope someone can give me the right advice.

I'm currently stuck in a RECOVERY boot loop. This happened after I did a Factory Reset including an internal memory wipe from INSIDE Android. then when the phone rebooted I was greeted by my installed Recovery, TWRP (I think I am, or was on version 2.7.0.2). So when TWRP starts I see TWRP's boot screen, then it flickers off and appears again. It loops through this until I pull the battery. So I never get the TWRP menu. When I try to turn the phone on normally, or into Recovery mode (Vol Up + Home + Power) I get the same TWRP boot loop. The only different powering on mode I can do is Download mode (Vol Down + Home + Power).

I've attempted to update TWRP to the latest version (2.8.6.0) by entering Download mode, then pressing Vol Up to ready phone for a download. I plug my phone into my PC via USB. Then I open Odin (3.07) on my PC, add the latest TWRP TAR file in the PDA button, then click Start. All appears to be fine, Odin does it's thing, the phone restarts, but I am greeted by the same TWRP boot loop. Maybe I'm not flashing the latest TWRP correctly? It's been a very long time since I've done this.

I would really appreciate some advice on this! :)

EDIT: I think I have to use Odin to flash Stock ROM. This post makes me think that: http://xdaforums.com/showpost.php?p=36647313&postcount=6 I have a Stock ROM file that I used for this phone some time ago, it's Android 4.3. Will I have any Android version issues since I was on Android 5.0.2? I'm guessing not because I did a factory reset, plus flashing the Stock ROM will also do a wipe if I tell Odin to, right?
[Galaxy Note II Q&A, Help & Troubleshooting] tetakpatak:
Strange are the issues from 1st part of your post. Could it be, that you have wiped the system? Or that your battery is dying? But the download mode worked fine, right? What happens if you connect with the charger when the phone is switched off?

Flashing a stock 4.3 should work fine if you have never flashed knox bootloader (stock 4.4). Odin will wipe everything except the files on storage, so don't worry about that part.

tetakpatalked from N7100
[Galaxy Note II Q&A, Help & Troubleshooting] invertedskull:
Yeah, I might have wiped the system, as I did select to wipe the internal memory during the Factory Reset (from inside Android). Does CM 12 allow that option though? It's prolly what happened, but doesn't explain the TWRP boot loop...

When I connect the wall charger when the phone is off it automatically turns on and goes into the TWRP boot loop. :(

Funny you mention the battery. It could very well be a factor as my girlfriend and I have had battery issues lately. She uses a Galaxy Note 2 also, but she has N7100 (mine is N7105). Her battery started draining ridiculously fast, and charging incredibly fast. Since I had a spare battery, I gave her the spare while I tried to rejuvenate her battery. It didn't work out well for my phone. I don't know what happened, but I ended up having to do a clean install, and since I was having some other issues with the ROM I was using, I went from Omni ROM Android 4.4.2 to CM 12 Android 5.0.2. Then I was fine. But I've always suspected I have a memory leak or some sort of file corruption in my phone's system. That might explain this issue.

Prior to this my original battery was showing similar symptoms as my girlfriend's battery, but not nearly as bad. So neither of us are using her crappy battery anymore, but I still have my original and she has the newest battery. I just tried booting my phone with the newest battery (it was on 75%), but I still got the TWRP boot loop. Then I tried with my battery while it was plugged into the wall charger, no dice either. :(

Ok, I'm attempting to flash Stock ROM through Odin now...

EDIT: Actually, I'm a bit concerned about using the Nand Erase All option in Odin. It should be fine to have this enabled while I flash the Stock ROM, right?
[Galaxy Note II Q&A, Help & Troubleshooting] beeshyams:
Hi and thanks for this thread

Hoping to get a solution to my problem that is driving me mad.. Literally

My old N7100 was flashed with Deep Impact ROM not many know this ROM but it is fantastic. Got 36 hours with 8 hours SOT and one hour talk time. I am a big battery freak.

Before selling that phone took TWRP nandroid of that and switched to another note 2, flashed nandroid (which was lying idle at home also n7100. )Now I put a new original battery hoping for better battery life

To my utter disappointment, I get very fast battery drain and barely 22 hours with 5 hours SOT. Similar result with another battery. Tried everything like battery calibration, cleaning caches, no rogue apps.

What I suspect is hardware problem but not sure. Any idea on how c to go forward

Please help and thanks in advance
[Galaxy Note II Q&A, Help & Troubleshooting] tetakpatak:
OK, it doesn't sound actually bad to me yet. I have asked you those few questions due to similar problems some other people had.

Regarding what you wrote, the most likely answer for me is that you have accidentaly erased the system. System partition of just every ROM can easily be wiped in any custom recovery.

You have two options:

1 try to dirty flash just your rom.zip in recovery and reboot

2 Your bootloader seems to be unknoxed, as automatically turning on on charger is a bug by Samsung's JB bootloaders, which didn't have knox crap until NDx I think. So yes, you can flash a stock JB not newer than MJ5. Use rather Odin 1.85 or 3.04 and just check auto-reboot and reset time, nothing else.

tetakpatalked from 1+One
[Galaxy Note II Q&A, Help & Troubleshooting] censored000:
No more LTE/3g/2g help help

Please help

my note 2 gt-7105 doesnt have LTE/3g/2g

after I custom rom my note 2 to CM12-20150416

kernel version 3.0.64-CM-ga0d78f8

before status was fine, I was able to use my data 3g/LTE then some error occurs and no more data.

Please help.
[Galaxy Note II Q&A, Help & Troubleshooting] invertedskull:
I think I might only have one option because I cannot get into Recovery / TWRP. So Flashing Stock ROM through Odin is my only option, right? Unless it is possible to dirty flash say, CM 12 through Odin while my phone in in Download mode. I am not aware I can do that? Anyways, I'll go the Stock ROM way...

EDIT: So I did the Stock ROM through Odin, all seemed to have gone fine, BUT the phone is stuck at the Samsung logo boot now... Doh! Here's a readout of the Odin Message:

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N7105XXUEMKA_N7105OPSEML1_N7105XXUEMK3_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> sboot.bin

<ID:0/007> NAND Write Start!!

<ID:0/007> tz.img

<ID:0/007> boot.img

<ID:0/007> recovery.img

<ID:0/007> system.img

<ID:0/007> modem.bin

<ID:0/007> cache.img

<ID:0/007> hidden.img

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Removed!!

<ID:0/007> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

2ND EDIT: I pulled the battery since it looks like I'm in a Stock ROM boot loop now. I attempted to get into Recovery (Vol Up + Home + Power), and it worked, I've got Stock Recovery. From here I wiped the partition cache and then attempted to dirty flash CM 12 from my ext SD card. It failed with some message about "E: Signature Verification Failed". What does this mean? Maybe I cannot use Stock Recovery to flash CM. So I'm now I've pulled battery, going to copy TWRP to my ext SD card, try flashing TWRP, then CM 12.

3RD EDIT: Still getting "E: Signature Verification Failed" when I try to flash a recovery... I've tried a few older versions of TWRP I had since when I last did this sort of thing to the phone, and I also tried a ClockworkMod Recovery, but all give the same "E: Signature Verification Failed". Then the phone reboots, and I am stuck in Samsung boot loop. At least now I have some kind of Recovery working, and I assume Download mode is still working. I just need to find out where to go from here...

I have another Stock Rom I could flash, it's Android 4.1.2. Is it worth trying even though I just flashed 4.3? Maybe I no longer have root since doing the Stock ROM. I feel like an idiot just asking that, I really should know! :P Maybe I need to be flashing SU in Stock Recovery...? Hmmm, this video shows I could try flashing a Custom Recovery (TWRP or CWM) with Odin... Any thoughts readers?
[Galaxy Note II Q&A, Help & Troubleshooting] RickBala:
Hi guys

I've been trying to root my note 2 but failed

I've downloaded the ROM files, downloaded the USB driver even, but it just won't detect my phone when i plug in via USB.

I've gone into download mode, plug in phone, but it just wont detect my phone when i run odin v 3.09.

Odin shows a blue icon, instead of yellow or green icon

Did i do anything wrong? :crying:
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
try different port, pc, cable, odin version, install Kies and try again.
[Galaxy Note II Q&A, Help & Troubleshooting] invertedskull:
Phew! All is working again. :)

So I couldn't flash ClockworkMod Recovery through Odin because they only issue IMG and ZIP files on their website now, and Odin requires a TAR file. I did find a video on YouTube that apparently shows how to convert an IMG to TAR for Odin use, but I couldn't be bothered going down that route... So I flashed the latest version of TWRP Recovery (ZIP) that I was using until recently (yes the one that got me in the TWRP boot loop). And this flashing worked super smoothly. It actually flashed it so fast I barely saw the progress bar move! Then I rebooted into TWRP Recovery (yes, no boot looping!), then I flashed CyanogenMod 12 and GApps, and it's JUST loaded into Android right now.

Thanks for the help!
[Galaxy Note II Q&A, Help & Troubleshooting] KimLeeSeon:
Help!

Hello Guys, I am quite new in this forum and I know that my question might already be answered earlier by other people.

But the forum is just so dense and I am having a hard time to look for an answer so I posted here instead.

First of all my Note 2 is a Korean Variant known as SHV-E250L, a friend of mine have already rooted my phone to

Model number: GT-N7105

Android Version: 4.4.2

Baseband Version: E250LKLUEML1

Kernel Version: 3.0.31-1689847

dpi@SWDD3012#1

and some dates

Build number: DN2 v4 Beta2

DN3 V5 ROM

XXUFND3 V5+

Sorry if this is being a noob question but my friend already left abroad and he can't help me at the moment but I really wanted to make it to DN4 with the note 4 features and stuff. My question is can I use the CF-Autoroot using the Model Number SHV-E250L or should I just the GT-N7105 because that is my phone's current model number? I am quite lost here and if someone would be able to answer my query it would really appreciate it guys. Thank you in advance.
[Galaxy Note II Q&A, Help & Troubleshooting] invertedskull:
Since yours is still model N7105, I'm 99.9% certain you should treat it as a normal N7105.
[Galaxy Note II Q&A, Help & Troubleshooting] KimLeeSeon:
Hello thanks for your reply

Hi thank you for replying after waiting for 3 hours for a any sort of response.

I'm sorry if you misunderstood my question what I mean is my original model of note 2 is SHV-E250L

and when my friend rooted it to DN3 V5 it became GT-N7105

So, basically are you saying that i should still treat it as SHV-E250L instead of GT-N7105 eventhough it says in my settings that it is currently on N7105? Thank you so much!

Update*

Also can I directly go to DN4 eventhough I am currently on DN3 V5 ROM? Please help TIA!
[Galaxy Note II Q&A, Help & Troubleshooting] yusuf_adsas:
1) You should always treat it as your phone's model for flashing root..in this case; SHV-E250L

2) If your DN3 and DN4 have different ROM base (e.g. 4.4.2 and 4.4.4) a clean install is highly recommended. .

Sent from my handphone, not yours
[Galaxy Note II Q&A, Help & Troubleshooting] KimLeeSeon:
Thank you so much! You that was a lifesaver, on the contrary I soft bricked my S5-G900F..

This is the saddest day in my life.. :(:(:(

Anyway thank you so much for your reply. how can I increase your thanks meter? Thank you!
[Galaxy Note II Q&A, Help & Troubleshooting] yusuf_adsas:
No sweat buddy. And sorry about your s5 but you can fix it I'm pretty sure just head over to their thread to get help ;)

Sent from my handphone, not yours
[Galaxy Note II Q&A, Help & Troubleshooting] beeshyams:
Weird , first of it's kind (?) battery problem

[MENTION=4900679]Chayangkul99[/MENTION]

and other folks who may be able to give pointers

PLEASE HELP !!!!

Configuration

N 7100 -- t03g (India)

Bootloader- N7100DDUENA1

bASEBAND- N7100DDUFND1

ANDROID INCREMENTAL VERSION- N7100XXUFNL1

KERNEL- 3.0.101- INDIA-v-4.4.2 OC-INTL-STOCK_HYBRID KITKAT (latest Agni version)

ROM- wesam.othman- N7100XXUFNL1 and Deep Impact 2.52

Problem

battery drain with cell switched OFF is high . Tested with two batteries- with new battery around 1% per hour and old battery (but in good condition ) 1.4%. Tests done over a 5 hour period to determine baseline ( thread of [MENTION=5401012]Celestial Fury[/MENTION]) [/B]

Noticed when battery drain was high with a NEW battery and NEW Note 2 (not actually new but lying unused at home for 18 months). On my old Note 2 with same ROM(s) and OLD battery the performance was way superior. This is NOT related to wakelocks , rogue apps, draining sync,wifi, blue tooth etc since am talking of drain when cell is switched off. Incidentally have all those well under control andwith new battery have statistically zero wakelocks while cell is in sleep ( around 4 minutes over 8 hour period and giving me a drain of 1.2%, which is fine since it drains 1% when cell is switched off, so effectively drain is 0.2 % per hour)

To me (maybe wrong) it appears to be a hardware issue- Samsung service center is deaf to my problem once the phone is rooted. Googled and searched tons of threads on XDA but didn't come across this issue...maybe people don't test drain with cell switched off. Posting here hoping to get some pointers instead of opening a new thread to understand (want to start my first thread when i have something solid to contribute) :

a) Is it hardware as i think?

b) is it a known issue or is there any hardware check to confirm this and any fix?

c) Any other pointers
[Galaxy Note II Q&A, Help & Troubleshooting] DabLin:
wife's phone won't work? please help

I bought my wife a note 2 (n7100) thinking it needed on a new screen but turns out £120 later I was wrong, when turning on it shows the boot logo which then flickers across the screen and then darkness :crying: when I Google it it leans to a bad flash (correct me if wrong) I have tried to flash twrp recovery using odin but still the same, I can boot to debug mode but not recovery?? please anyone if you can help me or have I just waisted My hard earned cash on a door stop.

Damo
[Galaxy Note II Q&A, Help & Troubleshooting] aitvariux:
Can anyone help me with the catlog here? My phone is not going to deep sleep and APS like BBS doesn't show the wakelocks.

https://docs.google.com/file/d/0B9deUgT65pOvdjJyNUdzai1hcDQ/edit?usp=docslist_api
[Galaxy Note II Q&A, Help & Troubleshooting] Dhesi2001:
SOD problem

I am with DN4 + Agni 4.4.3kernel + V11 mod and getting SOD problem frequently . selected Laq..... governor but not solved
[Galaxy Note II Q&A, Help & Troubleshooting] tetakpatak:
Flash an entire stock JB with Odin

tetakpatalked from N7100
[Galaxy Note II Q&A, Help & Troubleshooting] Rickav:
Hey there folks,

Feel like a bit of a rookie for getting myself into this mess but here is the long and short of it: I was content with a custom 4.4.4 KitKat on my Note II (N7100 international variant) for a long time. I'd been following an unofficial CM12.1 build closely for this model and decided to make the jump today.

First things first, I updated TWRP from this list. Or at least I say I updated. What I actually did was misread the list and downloaded "twrp-2.8.6.0-t03gub.zip". Upon attempting to flash, TWRP initially complained so I continued this trail of errors by downloading TWRP Manager from the Play Store and updating TWRP from there. Which only served to worsen the situation by kicking my device into Download Mode indefinitely. Rebooting did nothing nor did the usual key combinations (power + home + up for recovery and power + home + down for download mode). Hence, I decided to resort to Odin and flashed the "twrp-2.8.6.0-t03gub.img.tar" through there. Yes, the incorrect t03gub version again. Naturally, I couldn't flash any of KitKat or Lollipop roms I had on the external SD card as TWRP assessed them to be compatible with only t03g devices while mine was registered as t03gub.

It was at this point I realised the error of my ways and went about correcting it by flashing the infinitely nicer "twrp-2.8.6.0-t03g.img.tar" through Odin and happy days (or at least a few minutes) followed as I successfully flashed the glorious 5.1.1 CyanogenModX rom. Subsequently, I noticed I had no telephone signal. Wi-fi fine. Bluetooth a-okay. GPS all good. Just no mobile network available. Quick trip to the Settings revealed this:

[IMG="Sim Settings Screenshot"]http://xdaforums.com/attachment.php?attachmentid=3311296&stc=1&d=1431548826[/IMG]

All those "not available" are really not a good sign. And that's why I've arrived seeking out any advice/guidance here. I believe (hope) that flashing the stock rom from Sammobile will "fix everything" since I vaguely recall fixing a similar problem many a years back. But that involves a download of over a gigabyte and undoing then redoing the whole CM12.1 rom flash. While still a potential solution, one I'd like to avoid for the time being due to the hassle. Thus, does anyone have any other solutions? Ideas to get around this? As you'd expect from any noob, I do not have an EFS backup (or any backup for that matter. I had decided on starting anew with Lollipop). Any help would be hugely appreciated. Many thanks for sticking all the way through.
[Galaxy Note II Q&A, Help & Troubleshooting] DabLin:
Thanks for the reply, I have just tried to flash back to stock (KitKat) but still the same boot screen flickers around and then screen goes blank? Phone does boot up as computer recognises it? Could it be that I need to go back towards jelly bean?
[Galaxy Note II Q&A, Help & Troubleshooting] Rickav:
Final update: It's all resolved. Simply put, I changed the recovery to PhilZ Touch V6.46.3 and decided on flashing the pre-rooted, de-odexed modded stock Ditto Note 4 V2.1 to resolve the mobile network issues I'd been having. From there on, I flashed the CM12.1 CyanogenModX I had originally wanted and that is me all sorted out.

Cheers.
[Galaxy Note II Q&A, Help & Troubleshooting] tetakpatak:
I just tought JB would be nice in the case you are no Knox fan.

tetakpatalked from N7100
[Galaxy Note II Q&A, Help & Troubleshooting] najeebebrahim:
Hi

Update your Rom with DN 4 V 2.1

update to the latest agni kernal (May 2015 updates are available now)

Check If SOD is fixed or not...?

Fixed go on and flash the MOD v11 as excatly mentioned in the OP of the Thread.

Note:

I recommend a clean Wipe Re flashing of ROM and Kernal using TWRP.

Back up all your important data before reflashing.

Clean Dalvik & cache and after Rom Flashing.

Hope this will fix your headache....
[Galaxy Note II Q&A, Help & Troubleshooting] RickBala:
Hi all

I've got a faulty note 2 from my nephew

I cant turn on my phone at all, stuck at bootloop the samsung logo thingy.

I've tried to flash the rom with odin all versions new and old, but it just says FAIL ... ( in capital letters)

I've removed Kies from my PC, reinstalled the Samsung USB drivers in my PC

I don't know if the USB debugging has been turned on? the phone just died on my nephew last week and I'm having it right now and I can't check if USB debugging is ON or OFF.

It just says USB device not recognized when i plug in the phone.

I've tried with different ports, different USB cables, all FAIL.

I've tried with the official ROM, I've tried with android toolkit, I've tried running all possible ROMS with Odin but all FAIL...

Please help me, I've run of out ideas.
[Galaxy Note II Q&A, Help & Troubleshooting] Nazato:
Everytime I reboot my phone, my baseband version turns to uknown and my IMEI disappears. I have to restore my efs every single time I reboot my phone. Why is that?.. I'm on DN4 v2.1 and the latest Agni kernel.

Nevermind, fixed it with GSII_Repair.
[Galaxy Note II Q&A, Help & Troubleshooting] tetakpatak:
Download mode works regardless of the USB debugging setting status.

It is only important to connect it once for installing the device, after the driver is installed.

If the motherboard or bootloader are defective, the phone needs new MB to work again.

To exclude driver related problems, a good idea would be to try to connect it to Linux PC and Heimdall when the phone is in download mode. It needs no drivers and if the phone is still fine "heimdall detect" will recognize the device instantly.

tetakpatalked from 1+One
[Galaxy Note II Q&A, Help & Troubleshooting] brkk620:
OMG

Dude same thing happened to me today and I tried lots of things, couldnt done it. I tried what you've said but still I cant get any signal. Did you miss a step when you were writing here maybe?

Please help =)
[Galaxy Note II Q&A, Help & Troubleshooting] slg1986:
Hello,

for my note2 what is the best rom? I have Cyano12 but have many freeze. With my phone i use internet, music, video and a rom for best battery!
[Galaxy Note II Q&A, Help & Troubleshooting] Rickav:
In that case, initially I had tried to flash the original stock rom from Samsung. You can find the whole list from the Sammobile Firmwares website from I where I tried various roms without any success. In other words, having flashed them with Odin, my phone simply froze on the boot logo screen indefinitely. The stock roms I tried were: 4.4.2 for UK, 4.3 for UK and 4.4.2 ND3 for France. Since none of them booted for me, it's hard to pin-point which one fixed the network connection issue for me, although I'm quite certain it was the 4.4.2 ND3 for France since I recall it fixing a similar issue many months ago.

It was only after none of them booted for me that I decided to transfer the latest DN4 V2.1, PhilZ Touch V6.46.3 and TWRP t03g V2.8.6.0 (a backup recovery is usually a good idea) to the external SD card then flash TWRP t03g V2.8.6.0 tar through Odin. Then, I kicked into TWRP recovery mode (since it wasn't booting anyway). There, I navigated to the PhilZ Touch zip file and flash it and rebooted into recovery again to land into PhilZ Touch recovery mode this time. From there, I wiped the phone clean to install a new rom then flashed the DN4 rom. Upon completed, the phone finally rebooted successfully and I had to setup the phone from scratch on DN4. Was surprised to find the network signal issue had been fixed completely so I could exchange texts and calls again.

At this point, I transferred whatever I needed for the custom CM12.1 rom (the ROM, SuperSu, GApps, any other mods you use) and booted into recovery one more time to flash the latest TWRP zip (personal preference, you can stay on PhilZ Touch), wiped everything in internal storage, data, system etc, then flashed the CM12.1 rom, flashed GApps, flashed SuperSU then rebooted for the last time and set up the phone once more through CM12.1. In my case, the network connection fix seemed to carry over into the CM12.1 rom and all was well. Hopefully, you have a similar fate!