Ok so this morning I get a notification on my phone to for a software upgrade, so i'm like ok cool. Had my WiFi hooked up and everything and then when I try to install the update it stayed frozen on the white update screen and didn't even start the process of downloading or installing anything. So I call t-mobile and they tell me to take the battery out of my phone and try to turn it back on, unfortunately now my phone is booting up and as soon as it hits the software update screen it shuts down and loops.
Master Reset does not work! TRUST ME!!! IT JUST KEEPS LOOPING
After finding out I should have never taken the battery out and trusting T-Mobile I was like damn, should have used kies, I downloaded but it since my phone is looping, kies will try to connect but my phone keeps connecting and disconnecting because it's boot-looping.
Basically T-Mobile broke my phone, and after talking to 10 dumbasses they are finally sending me a new phone, here the problem, i'm do not want to loose my files...
What can I do to fix this problem? I have many important calls to make and I don't feel like waiting for this one in the mail.
All help is appreciated, I bet you know more then the tech support monkeys
Are u rooted?
Sent from my SGH-T989 using Tapatalk 2
AJ26T said:
Are u rooted?
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Rooted? I don't know what that is or how to do that, I have a stalk white galaxy s 2
Stalk? Straight talk? You sure its the T989? If so, i don't think you can return it to T-mobile if you dont have a contract with them.
--Possible remedies:
Odin stock recovery and stock gb.
Husam2011 said:
Stalk? Straight talk? You sure its the T989? If so, i don't think you can return it to T-mobile if you dont have a contract with them.
--Possible remedies:
Odin stock recovery and stock gb.
Click to expand...
Click to collapse
Well I got it from T Mobile but I never done anything to my phone, just used it as is.
If you can get into download mode, ODIN to stock and then do the ICS update via Kies.
belly1026 said:
If you can get into download mode, ODIN to stock and then do the ICS update via Kies.
Click to expand...
Click to collapse
X2, there are very easy to follow instructions here in the T989 development section here on XDA.
Just follow the instructions and you should be fine. If you cannot get it into download mode, you will have to get a USB jig to force it into download mode.
Either way, your phone is not hard bricked
Sent from my Nexus S using xda premium
Can someone please link me to that then????
How do I use ODIN to stalk? I think i downloaded the right riles, I click on PDA, open up the file and click start and get this.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
This happened to me a while back. With a. G2. Sometimes I wonder if tmobile technicians actually know what they're doing.
Sent from my SGH-T989 using xda premium
Restore phone via Kies if it will recognize your phone.
I don't know if this will work while you're boot looping but you can try.
1) Start the Kies program.
2) Under Tools at the top left go to Firmware Upgrade and Initilization and it will open up a pop up box asking you for the serial number and model number of your phone.
3) Take out the battery and look at serial number of your phone and model number (SGH-T989) and type it in the S/N and Model Name slots.
4) Put the battery back in and press both the up and down volume and insert the micro usb attached to your computer.
Hopefully Kies will do an emergency firmware recovery.
Questions go in the Q&A section
Try going into recovery mode and doing a factory reset, then try rebooting.
Hold the power button and both volume keys until the phone vibrates and the Samsung logo appears, then let go.
Only thing I can think of...
I have the same phone and i receved the update also. but my phone is rooted i set it for 6 hours and im unsure whats going to happen. What should i do? Should i let it update. or how can i stop it from doing so knowing im rooted?
tParsons, if you have a NON-STOCK recovery (e.g. Clockwork) on the phone then you WILL bootloop if you try to update. You must flash the stock recovery back before accepting the update or you're screwed.
The reason is that the first thing the new version does is try to run the update script, which fails as Clockwork doesn't know how to grok the stock update script process.
It's ok to be rooted (you'll lose root) but NOT ok to have a non-stock recovery when you get an update. Since the most-common way to get root on these devices is by using ODIN to put a non-stock recovery on the phone, accepting an update will almost-always result in a bootloop on a rooted phone unless you flash the stock recovery first.
I actually got the same notification today.
I literally JUST got my White SGS II myself yesterday afternoon (Father's Day Sale from T-Mobile) and spent last night loading it with all my APPS. I thought about going to ICS, but CoPilot Live does not work well (aka: Not at all) with ICS in my experience. That said, I delayed the update till tomorrow till I knew what the update was and popped over here.
Now I'm wondering what's going to happen when the update takes place tomorrow (I delayed it for 24 hours). Is my phone going to bootloop as well?
For the record, phone is completely stock. It's still running GB out the gate from T-Mobile (TouchWiz, Bloatware, and all) with the stock recovery, bootloader, everything. I haven't even had an opportunity to touch this phone yet. So I'm wondering if I'm going to get Bootlooping non-stop the moment it decides to force the update tomorrow.
CoPilot released a (free) update to CoPilot GPS and that version DOES work fine with ICS (I own it and use it)
If your recovery is NOT changed over (you DO NOT have Clockwork on the phone) the update should be ok. No promises, but I did it via KIES and all was good -- all I did was flash back to the stock recovery first.
Genesis3 said:
CoPilot released a (free) update to CoPilot GPS and that version DOES work fine with ICS (I own it and use it)
Click to expand...
Click to collapse
I am aware. It did not work for me on neither my gTablet (using a GPS Puck) nor my Motorola Xoom (both of which were running ICS). It did work for me under Honeycomb though. Apparently, I'm not the only one either. But that is a discussion for another topic. I merely mentioned it as an extraneous point.
Genesis3 said:
If your recovery is NOT changed over (you DO NOT have Clockwork on the phone) the update should be ok. No promises, but I did it via KIES and all was good -- all I did was flash back to the stock recovery first.
Click to expand...
Click to collapse
Well, the phone is (Currently) 2 days out the store from retail. I also carried over my Premium Handset Protection. Something screws up because of T-Mobile, they'll most certainly be replacing it.
Genesis3 said:
tParsons, if you have a NON-STOCK recovery (e.g. Clockwork) on the phone then you WILL bootloop if you try to update.
Click to expand...
Click to collapse
Hmm .. I've updated with Kies and Odin while I had CWM and never had a bootloop.
Related
Ok I'm stumped. Today my phone was acting strange (not responsive to button presses), so I tried to restart it, and it ended up in a endless reboot loop, only showing the "Google" logo. Then I looked into this thread: http://forum.xda-developers.com/showthread.php?t=1394051, and tried using Odin with the original factory images (OP's stripped image links dont work anymore) but it never passes the "NAND Write Start" part, so I had to pull the battery, and not it's stuck at the Phone-Yellow Triangle-Computer screen, from both Vol- + Vol+ + Power AND Vol- and Power combinations. I also tried using fastboot but adb never picks up the phone although all the drivers are installed correctly (I installed Kies).
The only thing that I can think of is getting a USB jig and trying Odin again, but is there anything else that I can try? Appreciate the help.
I had the same problem a couple of days ago. If Odin is having problems flashing a stock ROM its probably because of a faulty download or error while unzipping which aren't easily detectable. Try downloading the ROM again and extract. It worked for me. Also use a Windows 7 PC and update all the Sammy drivers and ADB drivers. Give it a try and let me know.
Uninstall Kies first. It's known to interfere with Odin!
Sent from my Galaxy Nexus using XDA
I've seen two other users with this exact scenario.
(Phone Triangle Computer).
I recommended a jig to both of them after shooting quite a few options down the pipe.
But never heard back if it worked or not.
Hopefully it did and will for you.
Exactly. Download the file again and plug phone in. You will see the (!)-------phone icon. Odin may not detect it but load ur file in odin and click start.
GNeX
AOKP
FRANCOS LATEST KERNEL
& WHATEVER [MOD AT THE TIME]
How hard can it be to use fastboot?
bk201doesntexist said:
How hard can it be to use fastboot?
Click to expand...
Click to collapse
Pretty damn hard if u ask the evo3D kids
GNeX
AOKP
FRANCOS LATEST KERNEL
& WHATEVER [MOD AT THE TIME]
Fixed
Jubakuba said:
I've seen two other users with this exact scenario.
(Phone Triangle Computer).
I recommended a jig to both of them after shooting quite a few options down the pipe.
But never heard back if it worked or not.
Hopefully it did and will for you.
Click to expand...
Click to collapse
I'm writing to tell you that I just went through what you were attempting to help this guy fix as well. I flashed a backward radio (stupid) and then flashed the wrong stock using ODIN. My solution erased my device - but since it was new I didn't care.. there may be another way to fix this that does not erase the device.
What I finally did to fix this problem was to open the CF_ODIN_YAKJU_IMM76D_full and manually remove the RADIO.IMG from there as ODIN will always fail on this -- and never return you to an operable state. I CHECKED the box to replace the bootloader (since this is screwed at this point). and it worked - I'm back to service. Now - I still have to get the correct radio installed, but I'll take cautious steps.
Thank you for your help. I did not try to ADB either - and still cannot attest to whether that will work on an ODIN fail.
Im going thru this same thing right now except Odin keeps hanging on this line>
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
Im stuck with ONLY the phone and computer icons with the yellow triangle and ! in the middle :-(
Don't mean to jump in...
Hey, XDA Community!
I have the exact same issue as the OP - a friend gave me his phone to tinker with because it was acting possessed. By that I mean it would start to boot, the Google text screen would come up and flicker (like in the horror movies), and then it would start going through the flashing colour loading screen and lock up a few seconds into it. The phone would become unresponsive and required a battery pull, but it wouldn't return to normal functionality.
I initially tried to get it into Recovery Mode to do a factory reset and data wipe, and even just getting to the screen would be a chore - it would get to the big Android but flicker and freeze before it got to the little android on his back. The couple of times I got to the little bastard I tried the factory reset but it would lock up soon after the process began. This all eventually led me to Odin because putting the phone into Download mode was the only thing I could accomplish consistently enough.
I think I ended up flashing a bad ROM because shortly after the phone locked up during the Odin flash I had to unplug and do a battery pull. After replacing the batter I got the infamous phone+yellow triangle+PC screen. Battery pulls, button combos, nothing worked to get it past that screen. The computer would no longer recognize the phone but it WOULD make the noise like something had just connected to it. A quick look into Odin showed that it somehow still recognized the phone. Several attempts were made to flash stock ROMs that I was 100% sure were safe for my phone, but all of them either failed immediately or hung at the "NAND WRITE STARTED" stage.
I ensured that I deleted ALL old Google and Samsung and TI drivers and reinstalled via the Naked Drivers package - still no luck. I'm at my wits end and am almost positive it's a hardware issue because some users have reported that it's a messed up motherboard or pooped out processor.
Still, I felt that I should at least post here in the hope that perhaps there's something I still haven't tried. Thanks in advance for any and all help/suggestions that anyone can offer :good:
Phone: Galaxy Nexus GSM i9250
Carrier: Fido
Unrooted; stock ICS ROM (4.0.4)
PS - I also tried OMAP Flash, Nexus Root Toolkit, and any attempts at using ADB resulted in nada.
I had this problem exactly! What caused it was trying to use a bad download file in odin so it got stuck and I had to pull the battery causing the dreaded yellow "phone-triangle-computer" screen. however I noticed that even with this screen on my phone if I plugged my phone in odin would still recognize it(the yellow box saying com:number showed up). So I just went and found a good download plugged it in to odin and started just like normal even with the yellow triangle screen I still got a blue progress bar and odin still flashed the entire thing and rebooted my phone 100% normal. Hope its this easy a fix for you.
airtime82 said:
I had this problem exactly! What caused it was trying to use a bad download file in odin so it got stuck and I had to pull the battery causing the dreaded yellow "phone-triangle-computer" screen. however I noticed that even with this screen on my phone if I plugged my phone in odin would still recognize it(the yellow box saying com:number showed up). So I just went and found a good download plugged it in to odin and started just like normal even with the yellow triangle screen I still got a blue progress bar and odin still flashed the entire thing and rebooted my phone 100% normal. Hope its this easy a fix for you.
Click to expand...
Click to collapse
Could you tell us which file did you flash with Odin?
Same problem
vermillion66 said:
Could you tell us which file did you flash with Odin?
Click to expand...
Click to collapse
I too have the same problem. Can you please tell us which ODIN did you use?
rajiga said:
I too have the same problem. Can you please tell us which ODIN did you use?
Click to expand...
Click to collapse
Which model phone do you have?
Sent from my Galaxy Nexus using xda premium
I have galaxy nexus GSM yakju maguro.
Hi friends!!
After my S4 decided to run away without insurance I had to revert back to my s2. It still had Hellybean on it so I upgraded it to PA 4.45 just to check it out on my phone. Then I went into the instructions on how to unlock the phone. I went to revert it back to stock ICS that it came with to do so and when I rebooted it gets stuck at the samsung logo that pulses. I can't get into recovery but I still can get into download mode but nothing works when flashed. I tried using ODIN for every stock ROM available and still nothing. I never bricked a phone before and this doesn't seem like one to me since the bricks I fixed before have never been able to go into DL mode without being jigged, Can somebody help me. I need this running asap for medical reasons. I'm a sitting duck without this phone if something should happen to me. I live alone and have no land line if I need to call 911.
ScottPomroy said:
Hi friends!!
After my S4 decided to run away without insurance I had to revert back to my s2. It still had Hellybean on it so I upgraded it to PA 4.45 just to check it out on my phone. Then I went into the instructions on how to unlock the phone. I went to revert it back to stock ICS that it came with to do so and when I rebooted it gets stuck at the samsung logo that pulses. I can't get into recovery but I still can get into download mode but nothing works when flashed. I tried using ODIN for every stock ROM available and still nothing. I never bricked a phone before and this doesn't seem like one to me since the bricks I fixed before have never been able to go into DL mode without being jigged, Can somebody help me. I need this running asap for medical reasons. I'm a sitting duck without this phone if something should happen to me. I live alone and have no land line if I need to call 911.
Click to expand...
Click to collapse
Are you trying to boot into recovery while you are plugged into a computer?
Sent from my SGH-T989
jrc2 said:
Are you trying to boot into recovery while you are plugged into a computer?
Sent from my SGH-T989
Click to expand...
Click to collapse
Of course not. But I think the problem may be that I didn't know that Kies was still installed in this computer.
And removing Kies didn't work either. I was talking to a guy that does jtag repair near me he said try that first. Gave me a pit file and it didn't help.
ScottPomroy said:
Of course not. But I think the problem may be that I didn't know that Kies was still installed in this computer.
And removing Kies didn't work either. I was talking to a guy that does jtag repair near me he said try that first. Gave me a pit file and it didn't help.
Click to expand...
Click to collapse
Here is something something that has worked for me twice. Use JOdin3 ( https://builds.casual-dev.com/jodin3/) Plug your phone in before going to the websute and put the TWRP tar file in PDA. Click start. It will say it needs to obtain a pit file. Click OK. Ignore the part about using in the download mode combo. It should bootloop your phone and you then might be able to unplug your phone and boot into recovery. I use this as a last resort but it has worked twice for me.
Sent from my SGH-T989
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've not done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Majin Kaioh said:
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Click to expand...
Click to collapse
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I have had my share of boot looping experiences, never from not doing any type of experiments with my devices. nonetheless myself and I'm sure many other people just do what was mentioned in the quote to alleviate that problem.
i know you (OP) mentioned you don't plan on doing any flashing, but i would do that before using insurance personally, even if there was no deductible
Majin Kaioh said:
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
Click to expand...
Click to collapse
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jack man said:
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
It won't fix what sounds like a missing or corrupted boot file, had to deal with it on a LG g3.. restoring a full back up or a plain reset had no effect.. it was either doing a full flash or flashing the boot files
for that phone it would randomly happen when the OTA tried to upgrade the device while it was rooted, took me 3 times of dealing with it before I realized OTA was still live
Small update. My local AT&T store has a replacement being sent to me. I'm unhappy, however, since its apparently a refurbished device. I pay for insurance that covers a new device if something, anything, happens. They're refusing to send me a new one for some reason that they won't explicitly state to me.
My loyalty with AT&T has wavered, and I will probably be on another network in coming months. I'm thinking Sprint so that I can least have an unlocked Note 4.
Regardless, since this device is being sent back, I decided to try and Odin flash it anyways. It did not work. Still boot loops at the Note 4/Android screen. Doesn't even load the AT&T logo. I'm fairly certain something is fundamentally broken with the device. Probably a factory error. It's never been dropped, and has been inside a hard case since day one.
Being that it is a manufacturing error, I'm not to angry about that. These things do happen. AT&T's treatment of me, however, is just unacceptable. I've been a customer for about eight years, and have been on Android since the Motorola Backflip. I upgraded to a Samsung Captivate and never looked at another manufacturor.
Are you able boot to the recovery menu?
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
i have the bootloop issue before to put *#9090#
the loop is every aprox 3 mins
some sugestion?ยก
sudoBacon said:
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Click to expand...
Click to collapse
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
thepinkpanter said:
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
Click to expand...
Click to collapse
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
sudoBacon said:
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
Click to expand...
Click to collapse
I already did it but by using Odin 3.09 pls. see http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391/page5
maybe I did something wrong
or from where can I get / download a different N910AUCU1COC4 ?
thanks again for your kind help
Hi, I'm kinda new to rooting android phone.I just got a galaxy s6 edge from tmobile and I would lIke to root the phone. Searching around the forum but still doesn't ubderstand how's it work. So I got a galaxy s6 edge, baseband version G95TUVU3DOI1, come with 5.1.1 SMG 925T. Question is if I'm root the phone will i able to restore back to stock firmware, will tmobile able to find out if I rooted or not? Because I'm in Jump! Program and plan to switch new phone next year. And its there any easy step by step guide to root the phone. I don't really care about Samsung pay, would like to have fingerprint sensor if possible. Thank you
Before you do anything, understand that you WILL TRIP KNOX AND BREAK SAMSUNG PAY. Also, it is your choice to modify your device and this process seems to work differently for differnt people, so if anything happens, it's on you. However, there are several threads here that can help you if anything goes wrong
Okay, make a backup of all your stuff on SmartSwitch
You're going to want to download ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451
Then you're going to want to download UniKernel v8 from here: http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395
Open ODIN on your computer and don't touch anything yet
Then you're going to put your phone into download mode by turning it off, then holding POWER+VOL DOWN+HOME until a blue screen appears.
Press VOL UP to enter download mode and connect your phone to your computer with the cable that came with your phone
Wait for the little box at the top left to turn blue
On ODIN, click the AP button and locate the UniKernel v8 file that you downloaded before
Once you've found it, double click it to fill in the AP field with the file
Click START and do not touch anything until it's done.
Your phone will restart and once it comes back up, you'll be rooted. It can take several minutes for it to fully boot, so give it time.
Now, this is optional, but if you want a custom recovery to flash custom ROMS, download TWRP onto your computer from here: http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
Flash that file through ODIN using the same process as you used to flash UniKernel.
This recovery will let flash custom ROMs. I recommend XstreStoLite as it is very good on battery life, but you will not be able to use WiFi calling or VOLTE. You can download it here: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Let me know how it goes.
Can I unroot in the future if I want to go back to stock?
Osui818 said:
Can I unroot in the future if I want to go back to stock?
Click to expand...
Click to collapse
Yes. You'll just have to download the latest firmware from here or Sammobile.com and flash it using ODIN
Thank you. One last question, any chance using Odin will brick the device?
Osui818 said:
Thank you. One last question, any chance using OdinYes there will brick the device?
Click to expand...
Click to collapse
Yes. There is a small chance, but the method I described is the exact same method I used on my device and I've had no issues. Even if you do, there is almost a 0% chance of a hard brick unless you touch something you're not supposed to touch, and if you do soft brick, there are a few threads here that should be able to help. More than likely flashing stock firmware will fix any problems you have.
thanks akw for the run through, I've been away from android for 4 months and ran back to it. just got this phone and wanna quickly root it.
eruscool said:
thanks akw for the run through, I've been away from android for 4 months and ran back to it. just got this phone and wanna quickly root it.
Click to expand...
Click to collapse
No problem, buddy. Hope it goes well for you.
Akw6190 said:
No problem, buddy. Hope it goes well for you.
Click to expand...
Click to collapse
i need help too. i am trying to use smart switch as my last resort but its not working(ish). after installing the factory firmware it says the device will restart, unplug and plug it again. on the phone it reset itself and then with the green android logo saying installing system then 1/3 of the loading bar it just says erasing then blacked out then back on bootloop. i can still boot to recovery mode and download mode.
godefroy28 said:
i need help too. i am trying to use smart switch as my last resort but its not working(ish). after installing the factory firmware it says the device will restart, unplug and plug it again. on the phone it reset itself and then with the green android logo saying installing system then 1/3 of the loading bar it just says erasing then blacked out then back on bootloop. i can still boot to recovery mode and download mode.
Click to expand...
Click to collapse
Where are you getting the firmware from? What version of ODIN are you using? What port are you using in ODIN to flash the firmware?
There is a Mega download of the DOI1 firmware somewhere around here. I recommend downloading that and flashing using the AP port in ODIN 3.10.7, using the cable that came with your phone. This is the exact method I used to return to stock with no issues.