Related
hi everyone,
i got my note n7100 on meteor in ireland. everything was great so i decided to root it like i did with my previous phone. i rooted and everything was grand. then i decided to install a custom rom (omega rom), installed grand. i used it for a while and then decided id like to go back to stock firmware and maybe root again. so i used triangle away to reset flash counter, done. then i used odin to try flash my stock rom but i got a message saying "incorrect parameters" if i recall correctly. so i thought it was the stock rom and tried another one i thought was correct and it flashed but hasnt seemed to work, i then flashed CWM and then wiped the cache and factory reset and such but it hasnt changed anything. i dont have a restore file unfortunately. so that is why i am trying to flash back to stock. the phone now will boot normal with a few jitters and frame rate. then if i try to use the keyboard to type it come up black and no letters so i am unable to type anything or text. but i can call. then when i leave it down for a while it just turns itself off and i have to turn it on again. im at a loss of what to do next. if i can get it back to normal i would love it and i wont be doin anymore rooting and such again ha. any help would be fantastic. thanks in advance.
very sad person a.t.m. :crying:
try doing stock recovery and clearing cache then reboot. if it still doesn't work, wipe data and do factory reset. should bring your N2 back to stock.
do all of these after backup, of course. good luck!
can you advise me on how to do a stock recovery please cheers.
Try to do a factory reset.
Sent from my GT-N7100 using xda premium
power down NOte 2, then boot up by just holding down power, home and volume up.. android robot should appear.
it should give you options and choose using volume keys and select using power.
try the 2 options mentioned above and it should solve your problem. :angel:
EdwardLawlor said:
can you advise me on how to do a stock recovery please cheers.
Click to expand...
Click to collapse
Did you make a nandroid backup before you flashed the Omega Rom?
If you wanna go back to stock go here to Dr.Ketans thread, it has all you need to get back to your meteor branded phone.
[All in one]Stock ROM N7100 +How to Root N7100 & Reset counter+ much more
http://forum.xda-developers.com/showthread.php?t=1896696
It should be easy for you to do as you have flashed the device already
factory reset stil doesnt seem to work, phone is still jittery making weird noises, booting up isnt smooth its jumpy and everytime i boot up it says snote closed unexpextedly. iv reset a gud few times and done other methods a few times and still the phone isnt the way it was out of the box..
EdwardLawlor said:
factory reset stil doesnt seem to work, phone is still jittery making weird noises, booting up isnt smooth its jumpy and everytime i boot up it says snote closed unexpextedly. iv reset a gud few times and done other methods a few times and still the phone isnt the way it was out of the box..
Click to expand...
Click to collapse
What stock rom are you using or where did you get it?
I got it from Sammobile.com it's the proper stock rom and as far as I can tel the phone has returned to stock but my csc is unknown and the overall phone is not working 100% when I try to use Odin wit the correct stock rom from Sammobile Odin says parameters are incorrect so I ended up just wiping the phone and cache and that's as much as in able to do so far. Used Odin v3.04 and v3.07 . In android recovery <3e> I have the android lying down with a red triangle out of his stomach, and #manual mode# applying multiple-csc... Applied the csc code : BTU Successfully applies mutli csc. Has this anything to do with why is not working properly?
Ok I flashed the revolution hd rom and its fixed the phone as far as I can tell. Only one problem persists is that when the screen goes off it takes two taps of the power button to come on, but at least the phone is usable. cheers for help so far and also with this problem.
Sent from my GT-N7100 using XDA Premium HD app
Okay, so I rooted my phone back in December and had no problems at all with firmware 4.3. I had this app called "Clean Master" I think, so it analyzed my device to clean up "unnecessary" files and such. I go ahead a clean whatever it had "cleaned" and then I noticed that when I went into settings that it started freezing for about a minute or so and had to force close the settings. It also started to restart randomly at times and it got to the point where I just got fed up and looked to the internet. I decided to use Odin to Unroot my phone because at the time that's what I thought was causing the problem. This is where I think (I know) I screwed up. Instead of flashing the stock firmware for the T-Mobile Galaxy s4 I flashed this "GT-I9500-XSE-I9500XXUAME1-ROOTED_MAY4". I think I used this file for rooting but I downloaded so many files to get the rooting to work that I don't remember. This file is neither an .md5 file nor a .tar file. I don't know what I was thinking and I regret the decision. I started the transfer of whatever file that was to my phone using the Custom ROM download screen, and it only took about 4 seconds and said it passed. It reboots but ever since has been stuck on the Samsung Galaxy s4 screen. Recently it now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I've tried connecting the device via Kies but IT DOES NOT CONNECT. I'm beginning to think that I've just completely destroyed the phone and will be needing to by another. Any help would be much appreciated. I've tried everything I know. I've wiped the cache, wiped the data and factory reset the phone, but it won't reboot correctly. I'm stuck people. What can I do?
Can you get into download mode?
Sent from my SGH-M919 using XDA Premium 4 mobile app
The Sickness said:
Can you get into download mode?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into download mode yes.
re:
NEKTAR11 said:
I can get into download mode yes.
Click to expand...
Click to collapse
#1: Find the Odin flash rom/firmware for your phone and load Odin with it.
#2: Put the phone into download mode.
#3: plug usb cable into phone and computer.
#4: after you see [COM:xx] light up click START in Odin.
#5: when it gets done flashing let it reboot, have patience.
Forget all about these cleaning utilities, you can do all the cleaning
you want once the phone works properly and once it's rooted.
Only use CF-Autoroot to root the phone for best and trouble free results.
Here is the direct download link for CF-AutoRoot:
http://download.chainfire.eu/328/CF-Root1/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
Good luck!
Misterjunky gives good instruction, if you can get into download mode your phone can be resurrected. In my early days of flashing, I thought I had created an expensive paperweight but the guys on here saved me. One thing, you may have to do a factory reset in stock recovery to get your phone to boot. Happened to me a couple of times.
Good luck.
Flash until you brick!
Ok, so I'm pretty sure I have the right Odin flash firmware, but it all goes really fast and after "aboot.mdn" it stops and it says FAIL. Ok so I tried the md5 file that came with the download and it went through fine, but It's still stuck on the Samsung Galaxy S4 screen. Do I need to restart the system now and try the firmware file?
NEKTAR11 said:
Ok, so I'm pretty sure I have the right Odin flash firmware, but it all goes really fast and after "aboot.mdn" it stops and it says FAIL. Ok so I tried the md5 file that came with the download and it went through fine, but It's still stuck on the Samsung Galaxy S4 screen. Do I need to restart the system now and try the firmware file?
Click to expand...
Click to collapse
Have you done a factory reset?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Have you done a factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I've done it more than I can count, yes.
re: do this next.
NEKTAR11 said:
I've done it more than I can count, yes.
Click to expand...
Click to collapse
Flash this TWRP custom recovery in ODIN then go into recovery mode and
do a full wipe, data, system, dalvik cache, cache and do a Factory Reset.
Here is the direct download link for the Odin flash TWRP recovery:
http://techerrata.com/file/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Once that's done go into download mode and flash the
stock official M919 4.2.2 firmware (tar/md5) file.
Good luck!
SO I went into recovery mode, but it stays on the "teamwin" screen.
Pull the battery out of the phone, then put it back in and try to boot into recovery again. Sometimes, the recovery will hang like you described. You might have to repeat this process again and again until you get into the main menu of the recovery.
Okay, so I'm sure I'm doing everything right. I flashed the twrp recovery it restarts my phone. I held the power key, home key, and up key on the phone and released the power button when it shows the text on the top left showing that it is going to start recovery. It goes to a "teamwin" screen but freezes there. Truthfully, do you think I will be able to recover my phone, or will I need to send it in to samsung and pay 70 dollars plus the damages?
Misterjunky said:
Flash this TWRP custom recovery in ODIN then go into recovery mode and
do a full wipe, data, system, dalvik cache, cache and do a Factory Reset.
Here is the direct download link for the Odin flash TWRP recovery:
Once that's done go into download mode and flash the
stock official M919 4.2.2 firmware (tar/md5) file.
Good luck!
Click to expand...
Click to collapse
Do you think the reason why I can't flash the firmware is because I upgraded to 4.3 and it brought KNOX onto the phone?
NEKTAR11 said:
Okay, so I rooted my phone back in December and had no problems at all with firmware 4.3. I had this app called "Clean Master" I think, so it analyzed my device to clean up "unnecessary" files and such. I go ahead a clean whatever it had "cleaned" and then I noticed that when I went into settings that it started freezing for about a minute or so and had to force close the settings. It also started to restart randomly at times and it got to the point where I just got fed up and looked to the internet. I decided to use Odin to Unroot my phone because at the time that's what I thought was causing the problem. This is where I think (I know) I screwed up. Instead of flashing the stock firmware for the T-Mobile Galaxy s4 I flashed this "GT-I9500-XSE-I9500XXUAME1-ROOTED_MAY4". I think I used this file for rooting but I downloaded so many files to get the rooting to work that I don't remember. This file is neither an .md5 file nor a .tar file. I don't know what I was thinking and I regret the decision. I started the transfer of whatever file that was to my phone using the Custom ROM download screen, and it only took about 4 seconds and said it passed. It reboots but ever since has been stuck on the Samsung Galaxy s4 screen. Recently it now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I've tried connecting the device via Kies but IT DOES NOT CONNECT. I'm beginning to think that I've just completely destroyed the phone and will be needing to by another. Any help would be much appreciated. I've tried everything I know. I've wiped the cache, wiped the data and factory reset the phone, but it won't reboot correctly. I'm stuck people. What can I do?
Click to expand...
Click to collapse
Are you sure some other people have tried this file on a t-mobile variant? because GT-I9500 is indeed for a galaxy s4, but it's for the octa chipset, which is completely different from the t-mobile variant of the s4 since the t-mobile version is similar to GT-I9505, which is a quad core instead of a octa core
Just to give you guys a heads-up, I fixed my phone, but not by the ways you guys suggested. Not that I'm ungrateful, I am very happy you all took the time to help me out and I appreciate the suggestions. Thank you so much.
Oh and I fixed it by going into kies, clicking on "tools", "firmware upgrade and initialisation", and proceeded to follow the steps and type in my Model name and Serial Number.Fortunately they had the ability for my phone to return it COMPLETELY stock.
Thank you!
NEKTAR11 said:
Just to give you guys a heads-up, I fixed my phone, but not by the ways you guys suggested. Not that I'm ungrateful, I am very happy you all took the time to help me out and I appreciate the suggestions. Thank you so much.
Oh and I fixed it by going into kies, clicking on "tools", "firmware upgrade and initialisation", and proceeded to follow the steps and type in my Model name and Serial Number.Fortunately they had the ability for my phone to return it COMPLETELY stock.
Click to expand...
Click to collapse
OMG thank you for this. I actually registered just to thank you for this, I thought I was totally boned.
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
I`ve finally managed to mess up my kernel after flashing numerous roms on my galaxy s3 T999. The problem is that my device has bootlooped and I can`t enter recovery mode (due to messed up kernel) and I don`t know where to find a Kernel which can be flashed with Odin.
Can someone please share a link to any kernel for s3 T-999 (it must be in .Tar form please) so that I can fix my phone. Thanks in advance.
I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.
audit13 said:
I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.
Click to expand...
Click to collapse
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).
You used ROMs from sammobile.com or updato.com?
audit13 said:
You used ROMs from sammobile.com or updato.com?
Click to expand...
Click to collapse
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).
Ashaz93 said:
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).
Click to expand...
Click to collapse
Ashaz93 said:
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).
Click to expand...
Click to collapse
Flashing the stock 4.3 rom was or wasn't successful?
audit13 said:
Flashing the stock 4.3 rom was or wasn't successful?
Click to expand...
Click to collapse
It was successful every time i`ve done it in the past but it was a mistake to flash it via odin after knowing the recovery is messed up and disappears a few minutes after flashing (doesn`t matter which one I flash, I`ve tried multiple recoveries but they all behave the same due to problems with kernel). I believe that is what caused it to bootloop. I then went on to flash stock 4.3 several times but it bootloops on the samsung logo every time. Now finally i`ve encountered a new error which doesn`t lets odin to flash ROMs or Recovery. It remains stuck at SetupConnection the entire time.
BTW This phone is a 5 year old device and is not my primary device (Ever since I got the LG g5) but still it`s very dear to me so I started this thread. I don`t use it as much as I used to before but I still want to keep it alive (as long as it doesn`t dies on it`s own).
I need to find a way to clean cache from PC. I don`t think there`s any other way to save a phone in this kind of situation.
Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.
audit13 said:
Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.
Click to expand...
Click to collapse
IT WORKED!!! :victory:
Unchecking everything except F reset time did the trick. How did you come with that ? You saved the day with that man. Thank you so much for showing up and taking the time trying to help me. I would not have been able to fix it without your help.
You should make an instructional thread for people facing this issue with Odin on any phone. I`m pretty sure it will help a lot of people who are stuck at SetupConnection when trying to flash ROMs. Thanks a lot for helping me out. I`d give you 500 if I had more accounts
Take care of yourself and keep up the good work audit13. :good:
Glad you got it working. We're here to help and learn from each other.
I learned the "uncheck" trick years ago when I started flashing the galaxy s2.
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?