Hi, first let me give you the background of my phone.
I bought it off eBay used and it came in an almost perfect condition, preinstalled with Gingerbread 2.3.6. The only problems known with the phone is that it won't get recognized by Samsung Kies, but it does by my PC. Onto the problem...
My friend introduced me to the Cyanogen Mod 9, telling me it could increase battery life, performance, etc. I was interested and wanted to install this mod. I first rooted my phone with a Zip off a tutorial and that worked flawlessly and I had Super User. I then installed Rom Manager and proceeded to installing the mod. He gave me two zips to put into my SD card to install for the Cmod and Google Play. Long story short, after wiping cache, data user, and every other wipe before installing these two zips, I was stuck in a boot loop with the Samsung Logo and Cyanogen Mod 9 Animation. I didn't think much of it and turned off my phone for the night, leaving it for the morning.
This morning, I tried going to Download Mode and flashing a stock os with Odin3 and it went from boot loop to soft bricked. It gave me a message to connect the phone to Samsung Kies in order for it to before restored, but the problem is that the phone isn't recognized by the program. I tried .tar files and it led to nothing on Odin3 because it wouldn't get past "Get Pit for Mapping...". I tried numerous times and on one occasion, I accidentally had Re-Partition ticked but the flash didn't go through so I unplugged my device. After that, the phone turned off and no response after that.
It won't turn on, no device recognized through USB or Odin3. I tried the wall charger to see if it was the battery's fault but it led to nothing. What are my options in reviving my Samsung Galaxy S2 ?
Yikes. Sounds hard bricked. I think your only option is to pay to get try a jtag recovery. Search the board on that.
Sorry man.
Sent from my SGH-T989 using xda app-developers app
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
yoft1 said:
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
Click to expand...
Click to collapse
Thanks for the replies! I was wondering how reputable is MobileTechVideos on doing JTAG repairs on bricked phones. Also, do you have a tutorial on how I can try to install Cyanogen Mod 9 again with the Dark Side cache wipe so i wont get the same problem again? Thank you.
Hello,
Well, hopefully someone can help me out with an issue. While I've rooted and flashed phones before this, I probably know just enough to be dangerous. So, I was planning on moving back to my EVO 4g and thought I'd like to put ICS or JB on the phone to use as my normal device. So Sunday, I started playing with different ROMs in the forums. After flashing several ROMS I had an issue start. The phone would go through the White 'HTC EVO 4g' boot screen, stay there a moment and then reboot. I tried to reflash that ROM and had no luck. The only way to get out of this loop is to pull the battery. After searching on the website all week, I've tried several ideas, however nothing works. The last thing I did was to basically go through the process of rooting the phone again. After I did the fastboot command, I put the su-bin-3.0.3.2-efghi-signed.zip file onto the SD card and used the recovery tool to install the ROM. After I did this, I restarted the device and no joy. However now the phone will only boot up to HBoot screen. I can get to recovery, however I can not put any ROMs on the phone. Any help would be appreciated. Thanks in advance.
Rob
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Robobob1221 said:
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Click to expand...
Click to collapse
Actually, No. So I went back and looked at the directions I was following and realized that the 'su-bin-3.0.3.2-efghi-signed.zip' file was not a ROM or recovery file. When it was flashed onto the phone the stock rom was still on the phone. So ... I sent the 'TeamDIRTremicsUXv1.3' ROM over to the SD card and flashed it ..... IT WORKED .... thanks for the help!!!!!
Rob
Good to hear!
Enjoy the Team D.I.R.T goodness!!
Happy flashing!
An enviousOG
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
Hey guys, basically, i'm new-ish to flashing, but i was able to do it following all instructions. Yesterday i installed an s5 theme from this site that caused my phone to have problems such as the wifi not working. I was reading that flashing a custom kernel might help, it didn't.
So i woke up, entered my TWRP custom recovery and stupidly factory wiped everything, now my phone wont get past the 'Samsung galaxy s III' screen, it just stays there. I have no idea what to do, i'm dumb enough not to make a recovery file before i started all this so i've ****ed up there.
If anyone can help me get my phone back i'll be extremely happy, i just want it working again! I have work in a few hours and really hope to fix it before then! Any help is appreciated.
well i posted this for someone else who wiped their phone, maybe it would help you. OR i got it all wrong. lol (i know, not so funny).
can you take your ext.sd card , put in different phone, download a ROM and whatever else you need. then place ext.sd card back in your phone and flash away? IDK, might work.
good luck.
err on the side of kindness
What mrrocketdog said, and you can flash a ROM with S5 theme already built in.. If you just want it back to stock, flash newest firmware for your device with Odin
Hello all,
I've got a Tab 3 7.0 T210R stuck on the Samsung logo with pulsing blue background. I've read through several Samsung boot loop help threads as well as the general Loop noob helper but haven't found a fix yet.
For my stuck T210R, What I've done & can do:
Was rooted with a "patched" stock UK ROM from last March [sorry, don't recall which]
Was running fine until after I tried to install from Play the TWRP Manager, I obviously did something bad! like select wrong device maybe
I can get into Philz, TWRP, & use Odin
I don't have a recovery back up [i really don't care about restoring back to anything - just want it to work, clean slate, ya know]
Tried a couple of latest ROM's through Philz and a stock ROM XAC-T210RUEAMK1-20131122134958.zip though ODIN. They seemed to be successful but I still can't get past Samsung logo
I've tried these ROMS that seem to load but ixna on successful boot afterwards:
ODIN: KIES_HOME_T210RUEAMK1_T210RXACAMK1_1304745_REV00_user_low_ship.tar.md5
Philz: Stock.rooted.deodexed.T210R.zip
Philz: TAB3-T210-HASSAN-ROM-V1.0-kitkat-4.4.2-Aroma-Mods-all Languages.zip
Philz: cm-10.1-20131209(1)-UNOFFICIAL-lt02wifiue.mine.zip
What's killing me is that loading new or stock ROM's SEEM to work - no errors or anything obviously indicative that I'll still be boot looping as soon as I restart. I'm quite desperate and thinking I'm truly bricked.
I haven't yet tried using ADB but if I can use ODIN and TWRP or Philz, will ADB do anything better than what I've already done? I haven't tried anything with the kernel as I can't really understand what to do there. I read and read and read the kernel threads but with my experience its really not as straight forward as rooting or flashing a ROM or software, and I could conceivably screw up worse! I'm mildly experienced at following guides to have rooted and ROM loaded a 1st gen Kindle Fire, Samsung SII skyrocket, S4, Tab 2 7.0, Tab 3 7.0.
No replies or interest? Please help
I'm I in the wrong forum? Did I offend someone? Could really use some input, please.
Any one seen this before? If you've any experience LOSING this battle, please speak up and I'll know to just resign to now owning a pretty white Samsung brick.
Boot to customed recovery under wipe choose format this will zero all partitions then redo
thanks!
andynroid said:
Boot to customed recovery under wipe choose format this will zero all partitions then redo
Click to expand...
Click to collapse
if i could find the "thanks" button I'd use it.
I'm traveling now but definitely try your solution. By "redo" I presume you mean load a ROM. When I wipe I also presume I'll still have custom recovery? I should still be able to ODIN, too, if needed?
thanks again
Yes exactly recovery will not go away once you have formatted the partitions you can now flash a new customed ROM or reflash original FW using Odin..Cheers
Hey buddy wanted to know if you ever found a solution for your issue? I am in the same bind you were in. Can you help guide me. I tried installing the same files you did and to no avail. I bought a Tab 3 T210R from eBay that was stuck in boot loop, I am assuming that it isn't rooted as when I would I went into download mode, it said the firmware was official.