Solution for random boot loop? (not from flashing) - AT&T Samsung Galaxy S II SGH-I777

I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-

Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.

I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App

I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App

Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?

Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk

Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App

I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?

Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.

hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?

Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App

Related

[Q] Stuck at vibrant screen after odin

Ok, I was restoring my phone to stock with odin following these stpes
Disable Voodoo
Odin to eugenes froyo that wont brick
sticks at vibrant screen
tried odining to JFD
odin completes but still hangs at the vibrant screen
I have tried with and with out repartition checked and I am able to enter and exit download mode freely, I have tried 3 differnt versions of odin and 2 different downloads of the pda and pits. Any help would be great.
EDIT, Odin is finishing at the pass stage when the phone attempts to boot Currently flashing the JI6 seeing if it works.
Still not getting anywhere, I have now tried to odin to eugenes froyo, JFD, JI6, all which end the same with out a boot screen, I can get download but no recovery.
From my understanding when you flash eugenes froyo that wont brick the boot animation should change to the international one, mine has not done that so I am starting to wonder if there is an issue with the flashes themself.
How long did you wait after flashing the stock firmware? The first boot usually takes a while after an Odin. Did Odin finish flashing everything to the point that it said restart in blue?
You can find instructions to revert to stock http://forum.xda-developers.com/showthread.php?t=734475
I've gotten myself out of some pretty bad "bricks" with JFD and ODIN... make sure you also use the stock .pit file and you can check repartition, use JFD and should fix you right up.
I have waited for 10-15 minutes after it says restart and then sometimes after it says pass, and I have done to jfd and stock pit.
left phone at boot fell asleep woke up hr or so later still at vibrant screen, still cannot access recovery but can access download mode.
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
iynfynity said:
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
Click to expand...
Click to collapse
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
ionic7 said:
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
Click to expand...
Click to collapse
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
iynfynity said:
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
Click to expand...
Click to collapse
Yes read the first post it says what i have flashed.
Charlie Brown said:
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
Click to expand...
Click to collapse
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
ionic7 said:
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
Click to expand...
Click to collapse
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
ionic7 said:
Yes read the first post it says what i have flashed.
Click to expand...
Click to collapse
try that again.
Sent from my SGH-T959 using XDA App
Im having the same issue with, "Data Wipe Failed" and have 0.00 space in Application storage but my phone reboots into eugenes 2.2 perfectly fine and works, but the application storage seems to be empty still...very frustrating.
cvibe88 said:
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
Click to expand...
Click to collapse
have changed usb cord, port, computer, have flashed jfd ji6 froyo that wont brick, 512 pit,513 pit,and they have not laughed at me in anyway they are sending my new phone now and a g2 to try out soo either way I have something soon. I also was going from axura to stock to a custom rom not from one to the other and I do know how to use odin, I know what I am doing just need help figuring this one out has to be something im missing or its just not gonna work. 50 odins and nothing kinda says it all.
I am in the same boat.. tried ODIN + stock ROM from various sources, nothing seems to work.. am I out of luck ??

Unexplained boot loop

Hi all, I hope you guys can help as I'm coming up blank here after days of trying to fix this.
First, yes I read this thread and a few people were reporting the same problem but the solution was always to flash a stock firmware with odin.
Right now my wife's phone is stuck in a boot loop, she doesn't do anything out of the ordinary with it, I rooted it when she first got it 3 months ago and then flashed a stock kernel to get rid of the yellow triangle and it has worked perfectly until last week when she told me it was stuck at the galaxy s2 logo. No problem I though, I'll just flash a stock rom with odin and all will be well.
Well it didn't work out that way, I've flashed the original firmware, an ICS leak, Villainrom 1.1 and XXKI3 multiple times, with and without pit file + re-partition. I've flashed the old bootloader and I've tried a few custom kernels as well, and multiple combinations of the above. Nothing is getting it past the boot loop. The only result I've had that is any different to how I started is with an ICS build I got a screen saying kernel panic upload (or something like that, I don't have that rom flashed at the moment). When I connect at this time odin recognises the phone so I guess it's in download mode.
I can't get into recovery mode so I can't do a factory reset, when I press vol-up, home and power I get a blank screen for a moment followed by the same boot loop. I can get into download mode and odin is reporting successful on every flash. When I flash a custom rom or kernel I get the yellow triangle, it goes away when I flash a stock rom or kernel.
According to my wife just before the crash android market reported updates available and she installed them. I don't know if that's related or not but she says when she went back to the phone it had hung so she turned off the phone, upon turning it on it was stuck in boot (the big animated purple S part of the boot) so she removed the battery and since then it doesn't get past the initial galaxy S2 screen, sometimes, depending on which kernel it's on, the galaxy screen goes blank for a second or two and then the logo comes back.
I've really tried everything I can think to try, warranty isn't really an option as I'm in Saudi Arabia and I've been told it will take 3 months to get the phone back, also I can't easily access a jig, I'd have to make one and I'm not too confident in my ability to do that.
If anyone has any ideas at this point please help, I can't think of anything else I can do here.
tl;dr random boot loop, tried flashing everything I can find, no recovery mode but download mode works fine, help!
davegene said:
If anyone has any ideas at this point please help, I can't think of anything else I can do here.
Click to expand...
Click to collapse
Flash a full wipe firmware and see if that helps, if you need one there is a link at the bottom of my insecure kernel thread.
Thanks Odia,
I just flashed the firmware at the bottom of your thread, I9100XWKE7_CL215725_REV02_user_low. Tried it twice for good measure.
Unfortunately nothing has changed on the phone, still can't get into recovery or past the galaxy s2 logo.
davegene said:
Thanks Odia,
I just flashed the firmware at the bottom of your thread, I9100XWKE7_CL215725_REV02_user_low. Tried it twice for good measure.
Unfortunately nothing has changed on the phone, still can't get into recovery or past the galaxy s2 logo.
Click to expand...
Click to collapse
Have you tried with repartition and update bootloader ticked?
I didn't tick either of those this time but I have ticked repartition with a different firmware that came with a pit file. Do I need a pit file or can I tick repartition without it?
Sent from my GT-I9100 using XDA App
davegene said:
I didn't tick either of those this time but I have ticked repartition with a different firmware that came with a pit file. Do I need a pit file or can I tick repartition without it?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You need a pit file, use the 1 from the other firmware.
Ok, I just tried XWKE7 again with a pit file with re-partition ticked. Also tried flashing the old bootloader again with update bootloader ticked.
No change I'm afraid.
davegene said:
Ok, I just tried XWKE7 again with a pit file with re-partition ticked. Also tried flashing the old bootloader again with update bootloader ticked.
No change I'm afraid.
Click to expand...
Click to collapse
Most strange, look like your off to service
That's most unfortunate, I'm in Saudi Arabia and they have quoted 3 months to get the phone back under warranty although in reality I'd be lucky to get it back at all.
Are my options really exhausted or is there anything extreme I can try?
I ended up making a jig and took it for warranty repair and they were able to do it locally, it only took a few days.
The curious thing is even though I repartitioned several times using two different pit files the sdcard partition was still intact.
I'm pretty sure I was doing it right and the yellow triangle was coming and going as I was flashing stock and custom kernels so the flashes were taking.
I don't speak Arabic so I couldn't ask how they fixed it but what do you think was the problem? I was very surprised to find the data intact, it even had the same stock ROM that I flashed before I took it for service still installed.
Anyway thanks for your help in this thread odia.
Sent from my GT-I9100 using xda premium
I'd love to know what they did.
Sent from my GT-I9100 using XDA App

[Q] Bricked Vibrant?

Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you

Bootloop. Can't get into recovery.

Not sure what the CM updater uses, but I have tried to update with Philz, got stuck in an installation loop of the update itself.
Tried to use my jig and flash back to stock right now, got into download mode and was able to flash back to stock, but right now, I got into download with the jig, flashed stock ROM, and got a bootloop but am UNABLE to get into any recovery at all.
Pretty screwed up. Really need some suggestions here, guys.
Any ideas?!
I can get into download mode and flash via Odin (USB drivers installed via Windows 8)
Flashes successfully, installs stock recovery, reboots into bootloop.
No idea how to fix it.
Not a noob here. Nothing is working.
Any suggestions would be greatly appreciated.
I had the same problem and I ended up finding a working CWM tar file that can be installed using ODIN and I was then able to boot into CWM fine.
This is the exact file name: recovery-cwmtouch-6.0.2.7-GTI9300
I don't remember where I downloaded it from, but if you Google the exact file name I am pretty sure you'll find it. Just flash it using Odin and you'll be good to go.
TarekElsakka said:
I had the same problem and I ended up finding a working CWM tar file that can be installed using ODIN and I was then able to boot into CWM fine.
This is the exact file name: recovery-cwmtouch-6.0.2.7-GTI9300
I don't remember where I downloaded it from, but if you Google the exact file name I am pretty sure you'll find it. Just flash it using Odin and you'll be good to go.
Click to expand...
Click to collapse
Well, now I'm even more f****ed than before, because I had a zero count, but after trying this, I got a custom count in download, and I still cannot get into recovery.
Nothing works.
Bye, bye warranty.
Edit:
The 6.0.2.7 version by MSKIP worked, but the updated one did not.
I got recovery, now I'll see if I can flash stock and recovery to get my counter back to zero.
Sorry to hear about the counter. I'd suggest rooting your device, installing Triangle Away, resetting your flash counter and then finally unrooting your device by installing stock ROM from SamMobile or such. That's the best route if you want your warranty to remain intact.
TarekElsakka said:
Sorry to hear about the counter. I'd suggest rooting your device, installing Triangle Away, resetting your flash counter and then finally unrooting your device by installing stock ROM from SamMobile or such. That's the best route if you want your warranty to remain intact.
Click to expand...
Click to collapse
He probably needs a booting phone first.
But like he said, he's not a noob. He knows all that
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
He probably needs a booting phone first.
But like he said, he's not a noob. He knows all that
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Hi all,
I am stuck in the very same problem as of today!
I don't know what to do!
One more weird symptom is that when I tried to charge the Note battery..it suddenly went to bootloop again!
The battery was 100% at the begining of that damn update process!
I don't know what to do..all suggestions are so welcomed.
Iceberg707 said:
Hi all,
I am stuck in the very same problem as of today!
I don't know what to do!
One more weird symptom is that when I tried to charge the Note battery..it suddenly went to bootloop again!
The battery was 100% at the begining of that damn update process!
I don't know what to do..all suggestions are so welcomed.
Click to expand...
Click to collapse
If you have a Note, then advice we give here may not be relevant and may be unsafe.

Okay so I rushed into this and now I am in a boot loop

Been unlocked and rooted forever, had tons of ROMs loaded no issues at all. I sold my Note2 and in a rush went to flash it back to stock with Odin 3.07 and used this: ( KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 ) and followed this tutorial:
http://www.youtube.com/watch?v=4qtbEevn1VA&feature=youtu.be
I got into the boot loop like he did on the video but I can't get out of it. tried using the pit file he mentioned and that did not work and I tried to start over but no joy.
I was coming from a ParanoidAndroid 3.99 RC2. (4.3 if I recall).
There is no data on the phone, so I don't care how I get there I just need to be as close back to stock as I can get it, even if I lose root just want it working so I can give it to the person who bought it.
Thanks so much in advance. There appear to be a lot of options in terms of going back to stock but I am not sure what firmware/bootloader version that was on my phone, so rather than risk digging a bigger hole, I thought I would reach out.
I can get into Download without issue but that is it.
Odin mode shows SCH-I605
Custom Binary Download - NO
Current Binary - Samsung Official
System Status - Custom.
I try not to bug you all and have always been able to dig out of problems but I am low on time and don't want to try a solution that is not particular to my situation and make it worse.
Thanks so much guys, I appreciate it.
dawgpoundfan said:
Been unlocked and rooted forever, had tons of ROMs loaded no issues at all. I sold my Note2 and in a rush went to flash it back to stock with Odin 3.07 and used this: ( KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 ) and followed this tutorial:
http://www.youtube.com/watch?v=4qtbEevn1VA&feature=youtu.be
I got into the boot loop like he did on the video but I can't get out of it. tried using the pit file he mentioned and that did not work and I tried to start over but no joy.
I was coming from a ParanoidAndroid 3.99 RC2. (4.3 if I recall).
There is no data on the phone, so I don't care how I get there I just need to be as close back to stock as I can get it, even if I lose root just want it working so I can give it to the person who bought it.
Thanks so much in advance. There appear to be a lot of options in terms of going back to stock but I am not sure what firmware/bootloader version that was on my phone, so rather than risk digging a bigger hole, I thought I would reach out.
I can get into Download without issue but that is it.
Odin mode shows SCH-I605
Custom Binary Download - NO
Current Binary - Samsung Official
System Status - Custom.
I try not to bug you all and have always been able to dig out of problems but I am low on time and don't want to try a solution that is not particular to my situation and make it worse.
Thanks so much guys, I appreciate it.
Click to expand...
Click to collapse
Use the pit file and the KIES VRAMC3 that you already have to go back. Wait until the process is done and Odin reboots your phone and says PASS. When it reboots your phone and says PASS, pull the battery, boot into recovery, wipe data and factory reset then wipe cache and reboot. Should be good to.
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Use the pit file and the KIES VRAMC3 that you already have to go back. Wait until the process is done and Odin reboots your phone and says PASS. When it reboots your phone and says PASS, pull the battery, boot into recovery, wipe data and factory reset then wipe cache and reboot. Should be good to.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Duh, thanks dude, I appreciate it was silly and easy my bad.
do you
did you download the verizon software you get when you plug in your note 2 to your pc if so there is a repair mode put your phone into download mode and start it then you will need the pit file as for some reason when i have done this it boot loops but when its finished you will have a stock note2

Categories

Resources