yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] chiefsfan69:
Thank you JeramyEggs, The screen goes black and then flashes the note 2 screen bro. I believe it does reboot though. I was thinking maybe my volume up button wasn't working but I know it is for sure at the moment. By the time this is all said and done it may not be lol.

Edit: when doing these flashes in Odin the only options that should be checked are the "auto reboot" and "f.reset time" correct?
[Verizon Samsung Galaxy Note II] JeramyEggs:
I would check auto reboot off as well. What exact files can you flash in odin, and what files fail?

"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
[Verizon Samsung Galaxy Note II] chiefsfan69:
ok so the pit file will PASS, I've been able to flash that by itself only twice but it PASSED both times. I have also PASSED on the pit file with the root66...Then have PASSED on just the root66 file by itself....And I had the alternate restore file PASS but only once a couple days ago...So I think I am close to out of options lol...maybe I should flash the ones again that I can and post them in here just for future ref maybe if someone comes across a similar problem?? Thanks for trying to HELP me Jeramy!
[Verizon Samsung Galaxy Note II] chiefsfan69:
<ID:0/004> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> boot.img

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

<ID:0/004> cache.img

<ID:0/004> hidden.img

<ID:0/004> modem.bin

<ID:0/004> param.bin

<ID:0/004> recovery.img

<ID:0/004> sboot.bin

<ID:0/004> FAIL!

<OSM> All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy Note II] chiefsfan69:
You know I am kind of worried about the whole extracting the files. I don't know if a person can screw that part up but if someone can I might be the guy
[Verizon Samsung Galaxy Note II] andrewjt19:
It looks like you have a corrupted download. Redownload the Odin files from Imnuts post in Development and try it again. Also make sure you use the rear most USB ports plus maybe use the Odin from Adam Oultler's post about Bootloader unlock.

Scribbled from my Note II

www.projectintercession.blogspot.com

---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------

Also did you use the 3 button combo to reboot into Recovery?

Scribbled from my Note II

www.projectintercession.blogspot.com
[Verizon Samsung Galaxy Note II] chiefsfan69:
Thanks for your help Andrewjt19. I will give new downloads a try right now. Ive tried the bootloader unlock a bunch of times and can't seem to get it to pass but I will download a new of that as well. I'll update when I am finished. Fingers crossed. Yes It goes into a bootloop whether I try to just use the power button or try to use the 3 for recovery. It will only get into odin download mode.
[Verizon Samsung Galaxy Note II] andrewjt19:
I don't mean changing the bootloader our anything, just using the Odin version Adam links in his post. I also have found that if you get an error, leave the phone plugged in, while in Odin mode, restart the computer, restart Odin, try again. That usually works.

Scribbled from my Note II

www.projectintercession.blogspot.com
[Verizon Samsung Galaxy Note II] JeramyEggs:
When you redownload, verify the md5's if you can. That way yoy can rule that out. I dont think you are hosed at this point, just lost. I would think that getting onto download mode is crucial. You have that still. I just can't accept a dead note 2..... It hurts too much.

"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
[Verizon Samsung Galaxy Note II] chiefsfan69:
Lol thanks, yes it hurts bad. But yes it seems like majority think that too, about being able to get into download. Your right though lost as it gets. I just feel like I've flashed every possible thing I can. Would you say it's worth trying the jtag thing? I worry about that too though.
[Verizon Samsung Galaxy Note II] shangrila500:
JTAGing is an option but it should be your very last option. The community trusted person is MobileTechVideos, you can Google the site and talk to them about it.

Service doesn't matter at all when flashing with Odin, it has nothing to do with it.

---------- Post added at 12:11 AM ---------- Previous post was at 12:08 AM ----------

Honestly JTAGing is a last resort and is almost always used for hard bricked phones, yours is soft bricked at this pint but you could send it off and have it JTAGed. I honestly wouldn't, I think you are a little overwhelmed at the current moment and may be in a little over your head and that is why you're having such issues with Odin. I don't mean that in a bad way at all, we have all been there at one point or another.

Did you ever flash Root66 or the alternative recovery rom with the reboot option unchecked in Odin? Also what versions of Odin have you tried?

I saw you said you were trying to unlock the bootloader, or had tried. You don't even need to bother with that at the moment, even if CASUAL said it worked correctly you'd still be in a loop until you get Odin to flash the ROM (Root66 or the alternate restore) and stop it from looping. Once the looping is stopped and you can boot your phone then it will be time to use CASUAL to unlock the bootloader and root your phone.

As a couple of people have said, re-download Root66 and the alternate restore rom, unzip em, and check the MD5sum. I saw you said you were worried you may be messing something up when unzipping them, don't worry about that; just use 7zip to unzip them and then use a program to check the MD5 of the ROM you just unzipped. If the MD5 matches then you're good to go with flashing in Odin, if not re-download it until you get a matching MD5.
[Verizon Samsung Galaxy Note II] andrewjt19:
II agree, you definitely are not hard bricked, you may try to Download one of the newer stock Odin versions and try that instead of VRALLJB. I believe it's in imnuts thread as well. I've been where you're at and it's worrisome, but you're far from hard bricked. I've been there too. You may want to just try and reflash twrp recovery and just try flashing the stock rom.

Scribbled from my Note II

www.projectintercession.blogspot.com

---------- Post added at 07:14 AM ---------- Previous post was at 07:08 AM ----------

Use Adam's Odin file here, just unzip, navigate into the folder abs double click on Odin application, Do Not Remove any files..

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

I'll find the newer Odin from imnuts and post..

Edit: imnuts never posted the updated package. Just download the original Odin for again, check the md5 and make sure you flash it in the PDA section. By the way, there's no need to unzip the Odin file or add any pit files They're already included in the Odin zip. Just add, wait for Odin to recognize it, and start.

Scribbled from my Note II

www.projectintercession.blogspot.com
[Verizon Samsung Galaxy Note II] chiefsfan69:
You guys are extremely bad ass, and thanks a million for trying to help me out. Your absolutly right I am in over my head. I was lucky to have been able to root the sob. So no offense taken at all. Ok ill keep trying, so what kind of program can I get or use to check md5? so I dont need to extract none of the files?...also I'm doing this from a laptop as thats all I have is 2 different laptops, is that ok? Sorry for asking stupid ?s I just feel like im going in circles like crazy. So I have odin DL, the only file I should ned to flash is the root66 or the alternative? I haven't been able to get the alt to flash and pass yet, I dont believe, but the root66 usually passed
[Verizon Samsung Galaxy Note II] andrewjt19:
I've never used any root66 before, but if you download the stock image found below (or the alternative to keep it from locking the bootloader) and flash it with Odin under the PDA tab....

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

Scribbled from my Note II

www.projectintercession.blogspot.com
[Verizon Samsung Galaxy Note II] shangrila500:
This is from '11 but the program is what I use when I need to verify MD5s on my laptop:

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

Doing it from a laptop is perfectly acceptable, I have a XPS L702X I use for everything instead of going and booting up the tower.

Yes that's all you need to flash, you can try it with it without the PIT to see if that will help make the rom flash in Odin.

What versions of Odin have you used? If you haven't used 1.8.5 here is a link to it in my Dropbox:

http://db.tt/slXUyaci

It wouldn't hurt to try and see if you get any different results when flashing the files. If there is no difference just go back to the Odin version you got out of droidstyles thread.

Also remember to try it WITHOUT Force Reboot checked this time around.

Make sure that the drivers on your computers are the Sammy drivers and not the CASUAL drivers,

Here is a link about that:

http://xdaforums.com/showthread.php?t=2304481
[Verizon Samsung Galaxy Note II] chiefsfan69:
Awesome thank you guys, ill report back after work and trying again.
[Verizon Samsung Galaxy Note II] andrewjt19:
That's solid advice, on the other side, just learn from this, as we all do afterwards;) to remember to read, read read....

Scribbled from my Note II

www.projectintercession.blogspot.com
[Verizon Samsung Galaxy Note II] chiefsfan69:
Haha listen your the man even if you like such a team lol...really though thank you very much man...ill be off here in the hour and I'm stoked, you give me hope since you got yours...Ill update you all..you guys are studs
[Verizon Samsung Galaxy Note II] Digital DJ:
The best thing to do is step away from it fro a few when you get aggravated with it, then come back with a clean head...Don't try to keep at the same thing only to fail like the Chiefs...haha use a different strategy...lol:silly:
[Verizon Samsung Galaxy Note II] chiefsfan69:
I wasnt really sure how to figure out when exactly I rooted my note2 but I know now, The files used to root are still on here(duh) sorry guys. anyway so The date I rooted was 4/7/13 and I did things verizons way up to that point. So I'll try to figure out what download I'll need...again you guys are the ****(even you Charger)
[Verizon Samsung Galaxy Note II] shangrila500:
It doesn't really matter how you rooted your phone as long as you don't use the galaxynote2root.com method. I've seen the stuff from that site hard brick a few phones by destroying their EMMC.

What do you mean you did Verizon's way up until that point? Do you mean by accepting OTAs?

Also were you on VRAMC3 before rooting and unlocking? I think you have already answered that but I don't want to go searching. If you were on VRAMC3 before rooting and unlocking then the only 2 ROMs, Root66 and imnuts Alternate Recovery ROM, that you can use in Odin to restore your phone. The others *will not* work.

Have you tried flashing the bootloader in droidstyles guide yet?
[Verizon Samsung Galaxy Note II] chiefsfan69:
What does member op mean? Lol just curious "obnoxious prick"...yea I had done all updates up until that point. I wasnt thinking I was going to root the damn phone cause I figured I mess **** up(exactly)...but I have tried that bootloader and it failed..i might download and try again but I tgink someone up in this thread said not to worry about the bl right now

I wasn't on the very latest update but yes I was on the one before that, so I think your right I can only flash the 2...no luck so far and I've been flashing so awhile...I'll keep you all posted...It is passing in odin still but right back into a bootloop...
[Verizon Samsung Galaxy Note II] chiefsfan69:
<ID:0/004> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> root66_VZW_stock_system.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

<ID:0/004> system.img

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

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Completed..

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

<ID:0/004> Removed!!

Hmmmmmmmm I don't know guys Ive done the root66 and the alternate...Im going to keep going but they have all passed and right back to the loop
[Verizon Samsung Galaxy Note II] shangrila500:
OP means original poster.

Obnoxious prick?

If you weren't on the VRAMC3 update then you can use * any* of the restore ROMs in droidstyles guide. It would be a good idea to try the others out.

Did you ever turn Reboot of in Odin? If not you really need to try that! If that doesn't work you could also flash Root66 and check the Erase NAND (or whatever that options exact wording is) option. You should try the NAND option without changing any of the other options, SAVE IT FOR A LAST RESORT THOUGH!!!

And you shouldn't have to worry about the bootloader but sung as how you've tried everything else at the moment it wouldn't hurt to try flashing it with Root66 at the same time.

Try the VRALJB Odin ROM from droidstyles guide (direct link from the guide: http://www.androidfilehost.com/?fid=9390214368362234374), next if that didn't work try unchecking the reboot option in Odin when flashing Root66+PIT again, if that doesn't work try flashing Root66+bootloader, and finally if that doesn't work you could try flagging Root66 with the NAND Erase (or whatever the name is) option unchecked.

Just know that the NAND Erase could have potentially make the situation worse. At this point though you are already thinking about having it JTAGed so this would just make it have to go ahead and happen sooner rather than later.
[Verizon Samsung Galaxy Note II] chiefsfan69:
I was kidding about the meaning of the op...ok thank you very much sir, I will try all that and report back but it will be awhile. I am just very bummed I screwed this up and now have to bug every one for help. I am not trying to argue at all cause I know you are way above my level on all this but I thought in that forum for the return to stock said if you accepted either of the last 2 verizon updates you can't use them? Yes I have tried to flash with the reboot unchecked and just had to pull the battery and went back into the loop but ill def keep trying. Ill be very excited if I can use those other roms in droidstyle, as thats what our charger buddy used, right?
[Verizon Samsung Galaxy Note II] shangrila500:
You aren't bugging me or anyone in the community at all, you have a big issue and the community is here to help so hopefully you don't have to spend money getting it JTAGed. It is good that you are asking these questions because it show as us you are informed and that you have been doing your reading. The only time we get pissed off with people is when they post **** like this pretty much bragging about screwing up and committing fraud: http://xdaforums.com/showthread.php?t=2343210

Or when people refuse to do any research and want things handed to them on a silver platter and you have done neither of those and seem to be busting your ass big time trying to fix this and reading everything you can. That's what we like to see, it means the person actually cares.

Yes, VRALJB is the one the Chargers fan (I think his username is dead batteries? I'm too lazy to go back and check cause I'm using the XDA app and is have to copy everything I have written so far and I don't want to!) Used to go back to stock after nothing else would work so its a very very good idea for you to try it and see if it'll fix the bootlooping.

As I said before, but I want to remind you again, don't try the NAND Erase option until after you have tried restoring using the VRALJB and VRALL4 ROMs. I don't think it will cause any more harm to your phone, I've used it on my S3 before when I screwed it up, but it needs to be the very last thing you do this time after you have exhausted everything else just to be on the safe side. The reason I brought it up is because I was reminded in another thread that Root66 definitely doesn't wipe your phone completely, and I am unsure if the alternate restore does, so there is a possibility that something is still being left behind (for example a overclocking app that still has its preferences) that is causing the loop. That's why everyone here stresses the "DO NOT ACCEPT UPDATE AND DEFINITELY NOT THE 4.1.2 UPDATE!!!!!!" (That's not towards you, just an example of what people say regarding the OTAs) It stops us from being able to flash back cleanly to original stock and that's an issue when people have trouble like this.

Let me know what happens!
[Verizon Samsung Galaxy Note II] chiefsfan69:
Hey thanks a ton bro, you guys have all been a tremendous help. I am very new to rooting(obviously) and dont ever mean to step over the boundaries or rules. I am lucky to have all this help and I swear I dont want any thing on a silver platter(maybe a brand new note2 right now). I have lots to learn still but you guys have all taught me a bunch already. I will be giving all this another try around 5mst...I've been trying hard yes without success and my wife is honestly close to hernandezing my ass if I dont get it to work soonish...thank you again, I cant express it enough guys! Ill update you later
[Verizon Samsung Galaxy Note II] chiefsfan69:
Thank you all!!!!!saved my ass

shangrila500 YOU DID IT MY BROTHA!!! Thank you all, everyone that gave a helping hand and even just gave their 2 cents. I wish I could give you all big bear hugs....My phone is back up and running, thanks to you guys. Now since I believe I am back to stock and all, I still don't want to accept OTA updates is that right? and if I wanted to root again I could just do the Casual? Again Guys very much appreciated. I will post the download just to show what it did but I think it must have been the nand erase. I am STOKED.
[Verizon Samsung Galaxy Note II] chiefsfan69:
<ID:0/005> Removed!!

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> I605_VRALJB_Restore.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Erase...

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

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

<ID:0/005> boot.img

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

<ID:0/005> cache.img

<ID:0/005> hidden.img

<ID:0/005> modem.bin

<ID:0/005> param.bin

<ID:0/005> recovery.img

<ID:0/005> system.img

<ID:0/005> tombstones.img

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

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

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

SUCCESS
[Verizon Samsung Galaxy Note II] shangrila500:
HELL YEAH!!!!!

And yes, NEVER EVER accept OTAs. And yeah Casual will root ya and unlock ya! I would go ahead and do it if I were you cause Sammy phones like to go ahead and update themselves when you aren't paying attention.

I'm so happy you're back up and running!
[Verizon Samsung Galaxy Note II] chiefsfan69:
Oh and just so you don't think I'm too big of an idiot and so you know I didn't ignore you, I did try to do the root66 with nand erase, but it went back into the loop and it let me get back into download Mode so I just figured f it why not try it with the other too... I definently couldn't have done it without you guys, really do thank you guys very very much. By the way going from the note 2 to the fascinate is never ever recommended. .. It was brutal lol
[Verizon Samsung Galaxy Note II] JeramyEggs:
This makes me love xda all the more. See, I knew you would figure it out. Now I won't have to dump out a 40in remembrance of your note 2. No offense, but any time you have to use a facinate, it is brutal, even in 2010. Congrats
[Verizon Samsung Galaxy Note II] earled:
Sweet ive been following this topic since it started. Nice job guys. Nice to see the forum and the OP work together as a team and figure out the solution.

Sent from my SCH-I605 using Xparent Cyan Tapatalk 2
[Verizon Samsung Galaxy Note II] chiefsfan69:
Lol none taken. Yes drink the 40.. And XDA is absolutely full of genius' s and I will be forever in debt. .. so just to make sure, I can just use the same casual and other root downloads I put onto my phone in the first place right?
[Verizon Samsung Galaxy Note II] chiefsfan69:
Thanks man. .. They were the team, I was just the puppet...I learned alot and now after all said and done I'm grateful for the knowledge these guys have passed on
[Verizon Samsung Galaxy Note II] chiefsfan69:
shangrila500 , I can not believe this but It was doing the casual thing, causal then failed and now I am again stuck on a more rapid bootloop just the note 2 screen!!!WTF man maybe this is a sign I should stay away from **** that I don't know. Do you know why it would do this? I am trying to read up on it but I just figured maybe you had a input. F'ing BS.
[Verizon Samsung Galaxy Note II] JeramyEggs:
Usually whencasual failed on me, I jist reran casual again. Have you tried that?

"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
[Verizon Samsung Galaxy Note II] chiefsfan69:
Thank you for replying sir, No but I can't get out of this rapid fast bootloop, but can get into download once again and not recovery? man why does this happen to me? lol cause I'm a rook im sure but I have read and reread the casual and I still don't see where I could have went wrong. Do you have any advise or anything Jeramy

I can't run casual from odin, can I?
[Verizon Samsung Galaxy Note II] chiefsfan69:
So does anyone have any idea why this happened and I thought maybe I could just go that same route to get out of this bootloop but no luck?
[Verizon Samsung Galaxy Note II] shangrila500:
Some people have reran CASUAL when they said they were bootlooping, I have no earthly idea how they did that though. Can you clear all data in the stock recovery? Also make sure the driver isn't the CASUAL driver, a lot of people have issues in Odin because CASUAL overwrites the driver.