Develop Bugs

[Q] Problem with SGS and custom kernels

So I decided to try out the new cyanogen mod 7.1. I followed These instructions and everything went fine until it was time for the phone to reboot after heimdall's flash.
It didnt reboot, but stayed on the splash screen. I could still both boot in recovery (recovery was CVM) and download. I thought everything was ok, and put the cyanogen-update zip onto the external memory card. However, as all of you (and now I) already know, it doesnt work that way, as the zip has to be on the internal SD.
"Sucks to be me" I thought, but I applyed the update.zip that was already on the card, hoping that it would reset everything (did a factory wipe as well). It didnt.
So, I started kies, set the phone to download and hoped. Kies detects the phone, but it couldnt connect (it just tries infinitly). So, here comes the retard part: I found a guide for installing the same kernel with odin, so I tried that. Odin found the device, but stopped right after (SetupConnection). So, I pulled the battery, waited 5 minutes, and the dreaded "download error" came up. So I restarted the phone, tried to put it in download mode, and it worked! So, now Im back at square retard, becuase heimdall can still flash it and kies still finds the phone (without succeding in connecting), but it doesnt do anything else.
So: what do I do? At the present, I am prepared to settle for stock everything, as long as I get my phone back (I will probably try to install cyanogen again, and come back with new questions, but that is a later problem).
Thanks in advance<3

Prob better posting this in General or on a CM 7 thread/post...
You shouldn't have a problem flashing a stock rom with odin. Just remember to pick repartition, with the correct pit file for the rom.
Sent from my GT-I9000 using XDA App

Help? (Iv searched)

From the beginning:
Flashed CM 7. When it came out.
Was cool and all decided to go back to Jugs.
Put it on my internal and flashed (Wiped Factory, cache, delvik and formatted system)
Installation completed fine
Fixed Permissions and reboot
left it alone and didnt look at it for like ten minutes. I came back to it and it was off. So i thought atleast. It wouldnt turn on so i removed battery and replaced it turned on. Saw white Samsung. Cool sat it down and let it do its thing again
Came back to it. Off again. So i removed battery, replaced it and rebooted into recovery. Recovery came up fine. So i reflashed the rom. without all the wiping this time. Just flashed and rebooted.
Well same thing happened. I was able to connect in mounts to usb storage and copied over the unroot stock rom and flashed from external sd.
Same exact thing with this rom. Samsung logo would come up then nothing
So i got into download mode and hooked up to odin and flashed the only .tar i could find. Which i think is the only one on this forum. Tried 4 times and every time it fails at the end (at cache)... Removed phone after the 4th fail and pulled battery.
Tried to reboot into recovery and it brought me up to "ODIN MODE" saying "Firmware Upgrade encountered an issue. Please Select Revoery mode in Kies & try again" So i connected it to the computer and try to see it in Kies. It did not recognize it.
Odin on the other had still does recognize it. I can still attempt to flash the stock .tar but it always fails at the end "cache".
My phone will not boot. if i pull battery and turn on i get to this same "ODIN MODE". I cannot get into download mode anymore. I can only get into ODIN MODE.
Can someone please offer some advice on how to fix this. I have been looking for a good 2 hours and tried flashing this stock .tar for the last 3 hours hoping it will pass.
Thanks to anyone that can help.

Wait, unless I understood incorrectly, you didn't try a factory reset / flashing a different rom? You didn't have a nandroid back-up? (Sorry if I misread its very late here =p)

i did factory reset before trying to reinstall jugs.
Some how i got it to turn on. Odin the stock .tar. which failed at the end again like always. and then i odin stock recovery .tar that i had on my computer. this worked. so if anyone is ever having a similar problems
1. odin to stock. (it might fail at the cache section.)
2. odin stock recovery .tar
This should make it boot.

can't seem to flash anything in odin o_o

so, for some weird, out-of-the-blue reason, i can't flash anything successfully through odin. i tried flashing sfhub's el29 one-click ROM (no data) and it flashed, however, when it's done flashing and it tries to boot, it just bootloops. i used to be able to just go into recovery, wipe data, reboot, and all would be fine, however i can't boot into recovery. when i hold down volume up + power, it shows the galaxy boot ani for a few seconds like it normally does when going into recovery mode, but then it'll disappear, the screen will go black, and then it will try to reboot normally again. it never goes into recovery mode.
i tried flashing EL26 stock CMW kernel, and odin goes through the motions as if it flashes, however, when i try to boot into recovery, it does what it did before: display the galaxy boot animation for a few seconds, disappear, then reboots normally.
now, i'm trying to flash sfhub's fb17 full restore and it's hung at data.img (like only 2% remaining). it's been stuck for about 10 minutes now.
WHAT DO? should i try using Kies to reinstall stock firmware?

Your phone might be bricked with a failure of the data partition on your emmc
http://forum.xda-developers.com/showthread.php?t=1504808

dammit that really blows! i need to order a jig now to clear my count. dammit i knew i should've used the triangle app last night when i had the chance. blahhhhhhhhh

okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?

cnstarz said:
okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?
Click to expand...
Click to collapse
Good info of the location the count is stored : http://forum.xda-developers.com/showthread.php?t=1494114
Sent from my MZ505 using XDA Premium HD app

yeah, i saw that earlier, but i can't make anything of it.
i tried "/sys/block/mmcblk0boot0/force_ro" via adb while in recovery, but got access denied. is it because su isn't included in rogue 1.1.2 recovery? if so, how do i install su?

At least you should have the original bootloader so a jig will work.
To help others, do you think you can remember when the problem happened.
Usually it happens when doing operations in an ics-based custom recovery, operations like wipe/factory reset, restoring backups, flashing ROMs, etc.

i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.

also, apparently the only recovery image i can flash via odin is steady hawkin's rogue recovery 1.1.2.

Okay wtf im able to flash cm7 all of a sudden. Brb, blowing load into sock, will report back later.
nvm, it freezes about 5 seconds after loading the home screen.

cnstarz said:
i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.
Click to expand...
Click to collapse
I've never used calks format all with anything ics related because I heard you don't want to format the data. also when you factory reset was that on el26?

I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't

level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
check out this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
i've basically moved my discussion to that thread. there's a user who was able to recreate the datafs partition using some of the sdcard storage space with success, obviously at the cost of storage space. check it yo.

level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
Level27xrock,
To answer your question first, you're probably "hard" bricked. It's been posted many times that you'll be able to get into Download mode, ODIN *most* of the stock image and it will hang at data.img because a previous action that you did - suspected to be the CWM wipe operation but not definitively confirmed - caused a I/O problem within the embedded memory or eMMC. Please feel free to try this out on your own and verify the results for yourself - it seems that may be the only way of convincing you.
You can find out more in the thread linked above.
I hope you will read the threads more before you try again. Please start with the one that says "How Not To Brick Your E4GT" for example. You also missed the one that said ROM Manager is a no-no for the E4GT - believe it's in the Q&A forum.

If I read the earlier posts right, I believe something similar happened to my friend. He was on AOKP then tried to Odin FD05 and it wouldnt get past splash screen. He then went back to EG30 and ran that through Odin and it did work but if some ROMs effect Odin completely flashing and restoring a stock setup then we are going to have a new surge of problems
Edit..he did NOT wipe in ICS recovery either
Sent from my Nexus S 4G using XDA

[Q] Stuck on boot logo, no matter what??

Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...

Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

[Q] Stuck in boot loop, trying to return to stock, I think I need to use PIT file

Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.

i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.

edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.

invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.

Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?

invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.

Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!

invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^

Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!

invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S

Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.

invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk

Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.

Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem

same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally

woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop