I attempted to install a DK28 modem with odin to flash a rom and it got stuck. I tried a few other modems which all were the right ones for the Epic but also got stuck. I then got the 'phone-caution sign-pc' image and tried flashing back to stock and it also got stuck at param. It now will not show any indication of charging and will not go into download mode. Any ideas before I go to Sprint for help? Going to try keeping battery out for 3 hours and then we'll see but think I may have bricked it. Oddly enough I checked all the modems and roms and they were all the correct ones, odin just kept getting stuck.
FaultyMind said:
I attempted to install a DK28 modem with odin to flash a rom and it got stuck. I tried a few other modems which all were the right ones for the Epic but also got stuck. I then got the 'phone-caution sign-pc' image and tried flashing back to stock and it also got stuck at param. It now will not show any indication of charging and will not go into download mode. Any ideas before I go to Sprint for help? Going to try keeping battery out for 3 hours and then we'll see but think I may have bricked it. Oddly enough I checked all the modems and roms and they were all the correct ones, odin just kept getting stuck.
Click to expand...
Click to collapse
I just spent the better part of yesterday (nearly 10 hours) trying to unbrick my phone after using Odin. I was stuck with the "phone-cautionsign-pc" screen for a while too. Afterwhich I couldn't get my phone to boot beyond the Clockwork Mod Screen. I read that the cable was probably the culprit in several threads, so I tried two different cables (Samsung and Palm), but to no avail. Finally I went to Radio Shack and bought their most expensive gold plated micro-USB cable and low and behold my machine stopped the "unknown USB device" crap and Odin ran through perfectly.
In your case, you've got to get back into Download Mode (pull the battery and then bring it back up while holding the 1 key) and then I HIGHLY recommend you get the best cable you can and retry Odin.
I think what you are saying is that you can't get back into d/l mode even by holding 1 and pwr. If that's true, try this:
1. Pull battery, wait 30 seconds
2. Hold 1 and pwr
3. Insert battery while still holding 1 and pwr
Hope this helps. And yes, get a new cable before using Odin again.
I have gotten download mode back
I got back into download mode today at work but only have brief moments to test it cause I work at a hospital and I can't get Odin to recognize it yet, I think it is just the drivers on the computer not working, gonna try reboot of computer and will try again. Thanks for the responses, I'll let you know if I get it working again.
How long should this take?
I have access to the phone through download mode and am using Odin to flash to the stock DI18 rom, I got passed Param but it has been sitting for about 15 minutes on Recovery. I have attatched a picture if anyone can see if I have done something wrong.
I couldnt really see the.pic to well but if you are flashing the full tar file don't use the pit file. I've had it fail before just cause of the pit file. You only need that if flashing the kernel or modem.
Sent from my Evo killer!
musclehead84 said:
I couldnt really see the.pic to well but if you are flashing the full tar file don't use the pit file. I've had it fail before just cause of the pit file. You only need that if flashing the kernel or modem.
Sent from my Evo killer!
Click to expand...
Click to collapse
I am attempting this now without the pit file, any idea how long it should take?
Also Is there anyway for Sprint to be able to tell that I rooted and flashed it if I did a re-partition in Odin? I just don't want them to tell me they can see that I rooted it and they won't replace it if this doesn't work.
FaultyMind said:
I am attempting this now without the pit file, any idea how long it should take?
Also Is there anyway for Sprint to be able to tell that I rooted and flashed it if I did a re-partition in Odin? I just don't want them to tell me they can see that I rooted it and they won't replace it if this doesn't work.
Click to expand...
Click to collapse
When you flash to stock there is no way they can tell any of that. No need to repartition or anything, just flash to stock and your phone will be stock.
kenvan19 said:
When you flash to stock there is no way they can tell any of that. No need to repartition or anything, just flash to stock and your phone will be stock.
Click to expand...
Click to collapse
I am just wondering if the stock rom doesn't take and I try and get a new one with warranty, will they be able to tell and deny me a replacement.
Below is Odin log where I am at right now. I am starting to get a little frustrated and thinking it is not working. Is there an alternative to Odin? Should I just chance taking it to Sprint? Should I attempt a different rom, if so which one?
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> boot.bin
<ID:0/007> recovery.bin
The tar file has the wrong extension it is suppose to be .tar not .md5
Try removing the .md5 part. If you Sony know how to just google how to change extensions that's what I did and I worked perfectly
Sent from my SPH-D700 using XDA App
gtuansdiamm said:
The tar file has the wrong extension it is suppose to be .tar not .md5
Try removing the .md5 part. If you Sony know how to just google how to change extensions that's what I did and I worked perfectly
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok, trying this now, I changed the extension, hope this works.
Thanks to everyone that is replying and helping me out.
gtuansdiamm said:
The tar file has the wrong extension it is suppose to be .tar not .md5
Try removing the .md5 part. If you Sony know how to just google how to change extensions that's what I did and I worked perfectly
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No, .md5 is not the problem. All the .md5 does on the end of a .tar is force an MD5 check, which as we can see from his output completed successfully. The only thing removing the .md5 will do is prevent that check.
I've flashed plenty of times with the .md5, and it's a lot safer than flashing without.
C'mon man, don't give out advice if you don't know what you're talkin' about.
Well I gave up and took it in to Sprint, they are working on it and we'll see. It didn't go anywhere after recovery just sat there. I'll post if they fix it or if I need more help. should know in an hour.
FaultyMind said:
Well I gave up and took it in to Sprint, they are working on it and we'll see. It didn't go anywhere after recovery just sat there. I'll post if they fix it or if I need more help. should know in an hour.
Click to expand...
Click to collapse
Just don't mention any modification, and if they ask you about it, don't admit to anything.
did you try taking out the SD CARD i once bricked my epic and it woulnt charge nor turn on and needless to say coulodnt get it in download mode so i almost took it to a sprint store but then i had a feeling taking out the sd card would help and a few minutes after it did, so try that
Electrofreak said:
Just don't mention any modification, and if they ask you about it, don't admit to anything.
Click to expand...
Click to collapse
Yeah, I told them it just happened when I woke up today, reminded them I had to wipe it when the GPS update screwed it up. So they believed me that I hadn't done anything with it. The rep didn't question anything and the repair tech didn't talk to me.
So they couldn't fix it either and just gave me a new phone, for the wonderful new $37 cause they CAN charge you if they have to replace anything. If I wanted to send it to Samsung I might have got it for free but I needed it today.
Going to take a break on flashing rom's for a little bit until I can get a second sprint phone.
betterment66 said:
did you try taking out the SD CARD i once bricked my epic and it woulnt charge nor turn on and needless to say coulodnt get it in download mode so i almost took it to a sprint store but then i had a feeling taking out the sd card would help and a few minutes after it did, so try that
Click to expand...
Click to collapse
Yeah I had taken it out, nothing happened.
Thanks to everyone for replying and trying to help me out.
leatherneck6017 said:
I think what you are saying is that you can't get back into d/l mode even by holding 1 and pwr. If that's true, try this:
1. Pull battery, wait 30 seconds
2. Hold 1 and pwr
3. Insert battery while still holding 1 and pwr
Hope this helps. And yes, get a new cable before using Odin again.
Click to expand...
Click to collapse
Thank you you saved me with this info. My phone would not turn on after odin ee03 modem . Awesome
Related
So after installing midNIGHT ROM v5.2 and not having it be my cup of tea, i decided to do a nandroid backup of my stock EC05. After backing up, I received that weird error where android flashes over the Galaxy S boot up. I then went to Odin and tried to flash back to stock DI18. After many failures I am stuck and dont know what to do, I am receiving this error in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Sbl.bin
<ID:0/006> boot.bin
<ID:0/006> recovery.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am using SPH-D700-DI18-8Gb-REL.tar.md5 as my PDA file and it has worked 3 times before using Odin. I have tried different computers, USB ports, and cables. Im stuck and idk what to do. Your guy's input would be much appreciated.
Edit: I have also formatted my SD card as well
Did you use a pit file?
heroforme said:
Did you use a pit file?
Click to expand...
Click to collapse
Yeah I have tried with and without and still get the same error
I have modem tar files for dg27, dl18, dk28, ec05 and eb13 but can't figure out how to get it uploaded on here. I also have the eb13 update tool from the Samsung site before it was pulled although I can't seem to zip it and upload it either.
Did you pull the battery, hold down the power button for 30 seconds, put the battery back in, put it in download mode and try again?
Do you BONSAI?
Tommo153 said:
So after installing midNIGHT ROM v5.2 and not having it be my cup of tea, i decided to do a nandroid backup of my stock EC05. After backing up, I received that weird error where android flashes over the Galaxy S boot up. I then went to Odin and tried to flash back to stock DI18.
Click to expand...
Click to collapse
Your issue with your nandroid was because it doesn't backup or restore kernels, your phone was probably fine.
kennyglass123 said:
Did you pull the battery, hold down the power button for 30 seconds, put the battery back in, put it in download mode and try again?
Do you BONSAI?
Click to expand...
Click to collapse
Just tried that and received the same error. This really blows too seeing as how I forgot to get TEP within the 30 day that I first bought this phone.
epic4GEE said:
Your issue with your nandroid was because it doesn't backup or restore kernels, your phone was probably fine.
Click to expand...
Click to collapse
Well I'm glad I know that now. How do I fix it?
Samsung EB13 Tool
Here is a link to the Samsung EB13 tool. Mabye this will help. http://www.multiupload.com/6O8VK453T0
From this article
http://forum.androidcentral.com/spr...ints-samsung-epic-4g-official-froyo-eb13.html
Tommo153 said:
Well I'm glad I know that now. How do I fix it?
Click to expand...
Click to collapse
Fixing it would involve simply flashing a stock kernel which I have no idea where to locate that. One way would've been to flash drockstars stock rom and then nandroid over it.
Edit: If you can access CWR you might be try flashing something else first. You mentioned different USB cables, hopefully some of them are not samsung cables?
You might also look at these thread http://forum.xda-developers.com/archive/index.php/t-907261.html
Also, this might be worth a look http://forum.xda-developers.com/showthread.php?t=1042746
Tommo153 said:
Just tried that and received the same error. This really blows too seeing as how I forgot to get TEP within the 30 day that I first bought this phone.
Click to expand...
Click to collapse
Don't give up, your not bricked. Did you turn off your pc's anti virus? Try different cables? If it fails just keep pulling the batery, go back to download mode and reboot your pc and keep trying...your very close and far from bricked.
Akagami said:
Edit: If you can access CWR you might be try flashing something else first. You mentioned different USB cables, hopefully some of them are not samsung cables?
You might also look at these thread http://forum.xda-developers.com/archive/index.php/t-907261.html
Click to expand...
Click to collapse
I cant get into CW at all. I have two blackberry cables as well as my samsung cable. I will check out that link, thank you.
Should I be trying it with the pit as well? I read somewhere that the pit can brick BRICK your phone. I have been using it, just don't know if I should stay away from it.
Also is there a particular version of Odin I should be using? I have been hopping around from 1.70. 1.61, and 1.3.
Ive used Odin3+v1.61 with victory_8G_100528.pit a few times.
Also, I assume you've seen the sticky under development but if not here it is.
http://forum.xda-developers.com/showthread.php?t=773032
Thank you all so much, shes alive again! So for future users in the same boat as I was here's what I did to fix it:
Using Odin v1.61 I flashed just the victory pit and checked the re-partition box. After that passed I pulled my battery and threw it back into download mode. From there I flashed just the stock DI18 without the .md5 at the end, and 2:11 later it booted back to stock.
Thanks everyone who posted, especially Akagami.
^^Good deal man, glad you got it. Now hopefully cheech can get his running again.
Hello,
So I have been running |ROM|Paradox II|L.O.V.E|3|11|12| for the last 4 days and I woke up this morning with my phone turned off. I though maybe my battery was dead and plugged it in to charge. I booted it up and it got stuck on the Darkside Kernel page. I took the battery out and tried booting my phone and nothing. Ever since then I have tried everything from Odin, etc. I get nothing, the phone will not turn on at all. not even into clockwork recovery mode, nothing will show up on the screen. I have looked in forums and have no luck.
Anyways I called T-mobile up and I spoke with a tech. They only asked me if dropped the phone, an physical or water damage, or if any pin connectors are bent. All of those answers are no. They never asked me once if the phone was rooted or modified.
So they are sending me a new phone for $20 warranty processing fee. They said I would be charged $120 if there was any physical or water damage, which there isn't.
My question is, has anybody returned a bricked rooted phone? Was there any issues with it?
I am fine with paying $120 worse case scenario. I am just wondering how would the know if the phone has been rooted if the phone cant even be turned on or powered on.
Does it start up and freeze on the darkside logo? That right there will tell them. I had a soft bricked phone. I could get into cwr so i just put a stock rom on the sd card and re flashed then unrooted it and sent it in.
Sent from my SGH-T989 using xda premium
Omnicide said:
Does it start up and freeze on the darkside logo? That right there will tell them. I had a soft bricked phone. I could get into cwr so i just put a stock rom on the sd card and re flashed then unrooted it and sent it in.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
It booted up the first time to the darkside screen, and now it wont boot up at all. I get nothing, no vibrate, no Samsung logo, nothing. I have tried all the battery tricks and everything. If I could get Odin or in clockworks recovery then I could fix the phone, but no luck.
I can get Odin to detect the phone by installing a qualm driver, but it will not install the UVKID rom. Is there a recovery boot loader or something else to install? I cant get the pass sign.
Not advertising for this in any way, shape, or form, but I came across this and you might want to look into it if you do not feel like sending it in to Samsung for a fix - http://www.youtube.com/watch?v=oZkIXj7cXNw&feature=player_embedded#!
Good luck!
Use this
http://forum.xda-developers.com/showthread.php?t=1513359
If you can get to odin then this will work...
Racing19969 said:
Use this
http://forum.xda-developers.com/showthread.php?t=1513359
If you can get to odin then this will work...
Click to expand...
Click to collapse
Thank you for your help,
When I try and install the rom it gets stuck at this point after 10 minutes of waiting.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVKL1_HOME_SGH-T989user_CL799405_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I have read online that some peoples power-board has failed and I believe that is what is wrong with mine. I cant get anything on the screen. Odin3 v.185 will detect it but I cannot get the green pass and it keeps getting to the same place. I have contacted the j-tag service but haven't heard back from them. I also ordered a usb jig off ebay, not that I think it will work, but I paid $4.50.
I have read in past forums with similar problems and they sent their phones in and got a new one or repaired by Samsung without any problems. I guess if T-mobile cant turn on the phone due to a bad power board, they have know way of know if the phone is rooted or not. T-mobile is sending me a replacement one shipping out tomorrow. I will keep you updated to see if anything else works in the meantime.
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.
Hello
I am in desperate need of help as I really need the phone in the next week. I am sure most of you are familiar with this problem, I'm not the first one, neither the last one to experience it. I am just going to say what happened, just in case.
Okay, well it was working perfectly fine until today, about 3pm; I had done nothing wrong. I have downloaded the new game Dungeon Hunter 4 or something like that and then played it for about 10 minutes give or take. Then I killed the application and didn't touch my phone for about half an hour. I was about to check the time and weather when I realized that my phone was stuck in this weird state which usually appears when you turn on your phone; with the Galaxy S3 screen logo. I could not turn it of so my first instinct was to pull out the battery, so I did. I tried to turn on the phone but it got stuck at the same point. Then I said to myself maybe it was the battery was not charged enough so I plugged in the cable. It opened to the battery screen which usually loads for a few seconds and then stars charging but this time it didn't; it was stuck in the loading mode.
I started to google it and see what causes this and how to solve it. I have tried most of the things but it seems as if all odds are against me. The home+vol-up+power wouldn't get me into recovery mode and it would only turn on the phone to the logo thingy. The home+vol-down+power would take me into download mode or whatever; so I tried Kies. It didn't work because at the end of the processing bit it would give me a message saying that the device was not recognized or something like that; therefore it would guide me through some other steps that I couldn't perform because I couldn't turn on the phone.
What is there left to do as I don't have any ideas left and I don't want to mess up the phone somehow; it is not rooted or anything, I had the original firmware on it.
Thank you.
PaulIvan said:
Hello
I am in desperate need of help as I really need the phone in the next week. I am sure most of you are familiar with this problem, I'm not the first one, neither the last one to experience it. I am just going to say what happened, just in case.
Okay, well it was working perfectly fine until today, about 3pm; I had done nothing wrong. I have downloaded the new game Dungeon Hunter 4 or something like that and then played it for about 10 minutes give or take. Then I killed the application and didn't touch my phone for about half an hour. I was about to check the time and weather when I realized that my phone was stuck in this weird state which usually appears when you turn on your phone; with the Galaxy S3 screen logo. I could not turn it of so my first instinct was to pull out the battery, so I did. I tried to turn on the phone but it got stuck at the same point. Then I said to myself maybe it was the battery was not charged enough so I plugged in the cable. It opened to the battery screen which usually loads for a few seconds and then stars charging but this time it didn't; it was stuck in the loading mode.
I started to google it and see what causes this and how to solve it. I have tried most of the things but it seems as if all odds are against me. The home+vol-up+power wouldn't get me into recovery mode and it would only turn on the phone to the logo thingy. The home+vol-down+power would take me into download mode or whatever; so I tried Kies. It didn't work because at the end of the processing bit it would give me a message saying that the device was not recognized or something like that; therefore it would guide me through some other steps that I couldn't perform because I couldn't turn on the phone.
What is there left to do as I don't have any ideas left and I don't want to mess up the phone somehow; it is not rooted or anything, I had the original firmware on it.
Thank you.
Click to expand...
Click to collapse
not enough info given on your setup to help you any further so the best I can tell you is to reinstall your drivers completely so your phone will be recognized. If it doesn't work try different usb cables, usb ports, another pc. There's many troubleshooting steps to consider. One of them is bound to help in identifying the device. Once it finally does just use ODIN to flash your phone back to it's factory firmware (stock). If you don't know how I suggest you do a bit more reading.
Sent from my Nexus 4 using xda premium
PaulIvan said:
Hello
I am in desperate need of help as I really need the phone in the next week. I am sure most of you are familiar with this problem, I'm not the first one, neither the last one to experience it. I am just going to say what happened, just in case.
Okay, well it was working perfectly fine until today, about 3pm; I had done nothing wrong. I have downloaded the new game Dungeon Hunter 4 or something like that and then played it for about 10 minutes give or take. Then I killed the application and didn't touch my phone for about half an hour. I was about to check the time and weather when I realized that my phone was stuck in this weird state which usually appears when you turn on your phone; with the Galaxy S3 screen logo. I could not turn it of so my first instinct was to pull out the battery, so I did. I tried to turn on the phone but it got stuck at the same point. Then I said to myself maybe it was the battery was not charged enough so I plugged in the cable. It opened to the battery screen which usually loads for a few seconds and then stars charging but this time it didn't; it was stuck in the loading mode.
I started to google it and see what causes this and how to solve it. I have tried most of the things but it seems as if all odds are against me. The home+vol-up+power wouldn't get me into recovery mode and it would only turn on the phone to the logo thingy. The home+vol-down+power would take me into download mode or whatever; so I tried Kies. It didn't work because at the end of the processing bit it would give me a message saying that the device was not recognized or something like that; therefore it would guide me through some other steps that I couldn't perform because I couldn't turn on the phone.
What is there left to do as I don't have any ideas left and I don't want to mess up the phone somehow; it is not rooted or anything, I had the original firmware on it.
Thank you.
Click to expand...
Click to collapse
I would take your battery out until you find a solution. Similar problem happened to me earlier this week...My battery died and made the whole thing more of a process than necessary. When you find a solution you want a good amount of battery left to flash the factory ROM. Walmart also sells a batter charger that allows you to adjust the power contacts. This basically makes it a universal battery charger.
Or you could always find someone with the same battery and ask them to swap you for an evening.
When I couldn't get past my sg3 screen I just went into D/L mode and flashed the .tar file from the Root66 instructions. Worked great for me.
re: a sure fix
PaulIvan said:
Hello
I am in desperate need of help as I really need the phone in the next week. I am sure most of you are familiar with this problem, I'm not the first one, neither the last one to experience it. I am just going to say what happened, just in case.
Okay, well it was working perfectly fine until today, about 3pm; I had done nothing wrong. I have downloaded the new game Dungeon Hunter 4 or something like that and then played it for about 10 minutes give or take. Then I killed the application and didn't touch my phone for about half an hour. I was about to check the time and weather when I realized that my phone was stuck in this weird state which usually appears when you turn on your phone; with the Galaxy S3 screen logo. I could not turn it of so my first instinct was to pull out the battery, so I did. I tried to turn on the phone but it got stuck at the same point. Then I said to myself maybe it was the battery was not charged enough so I plugged in the cable. It opened to the battery screen which usually loads for a few seconds and then stars charging but this time it didn't; it was stuck in the loading mode.
I started to google it and see what causes this and how to solve it. I have tried most of the things but it seems as if all odds are against me. The home+vol-up+power wouldn't get me into recovery mode and it would only turn on the phone to the logo thingy. The home+vol-down+power would take me into download mode or whatever; so I tried Kies. It didn't work because at the end of the processing bit it would give me a message saying that the device was not recognized or something like that; therefore it would guide me through some other steps that I couldn't perform because I couldn't turn on the phone.
What is there left to do as I don't have any ideas left and I don't want to mess up the phone somehow; it is not rooted or anything, I had the original firmware on it.
Thank you.
Click to expand...
Click to collapse
If you don't want to mess around trying this and trying that here
is a sure way you can get your phone fixed and working properly.
Here is the step by step guide:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone.
Here is the link to the Tmobile Stock Pre-Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Download the firmware of T999 Tmobile pre-rooted odin flash firmware
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
http://www.androidfilehost.com/?fid=9390169635556426451
Thank you for your quick reply. I considered doing this actually but I couldn't find the right firmware for T-mobile UK. Would the one that you post work for me as well? I tried to download the right one from "sammobile" but it didn't work. Whenever I tried to open them with PDA it said "The parameter is incorrect". What should I do?
re: firmware
PaulIvan said:
Thank you for your quick reply. I considered doing this actually but I couldn't find the right firmware for T-mobile UK. Would the one that you post work for me as well? I tried to download the right one from "sammobile" but it didn't work. Whenever I tried to open them with PDA it said "The parameter is incorrect". What should I do?
Click to expand...
Click to collapse
The Sammobile firmware is not exactly the same rom that I posted for you in the step by step instructions.
If you have a Tmobile T999 Galaxy S3 cellphone then the firmware I posted is exactly what you need to odin flash.
It's already pre-rooted so you won't even have to root the phone after you flash it.
Good Luck!
Hi
I have tried to install the stock official firmware you can find here on xda with Odin, but for some reason it failed.
It says this "<OSM> KIES_HOME_I9300XXEMC2_I9300OXAEMC2_1042335_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)"
For some reason it refuses to connect to Kies; could it be usb related issues ?
That firmware is not for your phone.
Then how can I find the right firmware for my phone? I bought the phone from a different provider with an option of network on T-mobile, so I'm not sure if I was using the t-mobile firmware. On download mode it says at binary "samsung official".
re: hmm
PaulIvan said:
Then how can I find the right firmware for my phone? I bought the phone from a different provider with an option of network on T-mobile, so I'm not sure if I was using the t-mobile firmware. On download mode it says at binary "samsung official".
Click to expand...
Click to collapse
How can anyone give you a useful answer if you don't even provide the model # of your S3
as well as letting every here know whether it's an unlocked and a rooted phone?
Yes, you're right, I'm sorry, my bad. My phone's model is the international one, the GT-I9300; the phone is unlocked and it can be used on any network; and as I said in the first post, it is not rooted, I didn't want to compromise my warranty or anything like that so it's unrooted.
re: Wrong Forum
PaulIvan said:
Yes, you're right, I'm sorry, my bad. My phone's model is the international one, the GT-I9300; the phone is unlocked and it can be used on any network; and as I said in the first post, it is not rooted, I didn't want to compromise my warranty or anything like that so it's unrooted.
Click to expand...
Click to collapse
You are in the wrong place if you have a GT-9300 and if you flash any roms found here
in this forum it will most likely brick your phone.
It is true that your phone will work on any network but none of the roms,
kernels and modems found here are compatible with it.
This forum is only for Tmobile T999 or other compatible models which your phone is not.
So if people give you download links or you find download links here to flash roms or other
things most all of them will likely brick your phone if you download and install any of them.
Here is the correct link for the GT-9300 Galaxy S3 phone:
http://forum.xda-developers.com/forumdisplay.php?f=1563
You will find everything you need in that forum including
roms, mods and help for any issues you may be having.
Good Luck!
Hey guys so I need some help as well. Something similar happened to me like the OP except mines a bit different.
My phone first started freaking out that it would turn the screen off soon after I unlocked it. Then the power menu would come up sometimes too so I thought that the power button might be bad? Then all of a sudden my phone turned off. I turned it on it got to the SG3 sign went away in a couple seconds and went black. Press power button again same thing happens. I've been able to get into recovery mode twice and each time my phone turned off again a few seconds after I was in.
I can get to the screen where you hold the volume down, power, and home buttons (not sure what its called bootloader?) it stays there for a while but eventually will turn off.
I think it keeps restarting itself too, it will vibrate and the SG3 logo will pop up for a second and go away. It doesnt restart right away though it takes like 30 seconds or so.
Now coming from the NS, I'm not familiar with Odin. I used it once to root and thats it. Havent opened it since November. Also if I remember correctly I wasn't able to root it on my Mac, it wouldnt work but when I did it on the PC it was fine, which I wont have access for, for at least 2 weeks.
The instructions on the first page, is that a viable option for me? Also do I need a PC or do you think a Mac will be fine? If not then I'll switch sims and go to my NS for a while.
ANy help is appreciated thanks!
okk so i'm trying to do this now but I'm running into problems. I'm doing what was said on the first page with using odin and putting in stock rooted firmware and I get my phone into download mode, I have odin set up click run then my phone screen goes black and on odin it says removed.
Now i'm not removing it, but here's the code from odin, and also when I hold the buttons to get back into download mode on my phone this is what I see note when i do this, i dont go through that screen where it says press volume up to continue, it just gives a ltl vibrate and shows this screen instantly. Try odin again and black screen again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
tankmaster90 said:
okk so i'm trying to do this now but I'm running into problems. I'm doing what was said on the first page with using odin and putting in stock rooted firmware and I get my phone into download mode, I have odin set up click run then my phone screen goes black and on odin it says removed.
Now i'm not removing it, but here's the code from odin, and also when I hold the buttons to get back into download mode on my phone this is what I see note when i do this, i dont go through that screen where it says press volume up to continue, it just gives a ltl vibrate and shows this screen instantly. Try odin again and black screen again
Odin code:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
root66_TMO_T999UVDLJA.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
aboot.mbn
NAND Write Start!!
boot.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
Removed!!
Click to expand...
Click to collapse
For anyone else who could be having this problem...
Honestly I had something similar to this before. Try a new USB cable and make sure it fits nice and snug. A loose one can cause this to happen. Don't forget to install drivers.
Sent from my SGH-T999 using xda app-developers app
TheLastSidekick said:
For anyone else who could be having this problem...
Honestly I had something similar to this before. Try a new USB cable and make sure it fits nice and snug. A loose one can cause this to happen. Don't forget to install drivers.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
When you say install drivers, does installing kies install the necessary drivers?? If not where can I get them from? And I'll try out different USB cables in a bit.
But I honestly doubt thats the problem, because even without the cable my phone keeps turning off as well.
tankmaster90 said:
When you say install drivers, does installing kies install the necessary drivers?? If not where can I get them from? And I'll try out different USB cables in a bit.
But I honestly doubt thats the problem, because even without the cable my phone keeps turning off as well.
Click to expand...
Click to collapse
You can get them off Samsung's site.
Not only try different usb cables but also try different ports and run through all the troubleshooting steps all over again on another pc if necessary. You've got plenty of options to experiment with. You just gotta find out which mix your phone favors.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
You can get them off Samsung's site.
Not only try different usb cables but also try different ports and run through all the troubleshooting steps all over again on another pc if necessary. You've got plenty of options to experiment with. You just gotta find out which mix your phone favors.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
+1. This in a nutshell.
Make sure you install the drivers for x86 if you're on a 32 bit OS, install the 64-bit driver on a 64-bit OS. You will know if you have done so correctly if you see SAMSUNG USB COMPOSITE DRIVER under ODIN. Good luck!
I got sick and tired of trying new ports, new PCs and new usb cables so I had mine sent away to samsung for repairs. The problem was just too complex for me.
Thank you for help anyway.
I'll get to another PC later to try it out, but I honestly think it has all to do with my phone.
Consider this, Odin fails everytime my phone screen turns off.
When I'm not plugged into the computer I turn my phone on it stays on that screen for about 10 seconds and then turns off. And every time I turn it on it does the same thing.
Someone told me my battery might be bad, I don't even know if I can charge my battery. To note I've been taking my battery out every time when I'm not using it. But last night to make sure its charged I plugged it into the charger. The same screen came up for about 10 seconds then phone went black turned off. I didn't get any indication that the phone was even charging. No LED light, nothing on the screen and every time I press the power button the phone vibrates that screen comes up and turns off in ten seconds.
Later today I'll put another friends battery in my GS3 and see if my phone stays on longer. I wont have a computer at that time, but I'll borrow her battery if my phone seems to say on longer then 10 seconds. That and I'll try my battery in her phone to see if theres any power in it and possibly make her charge my battery as well.
I think this may be more hardware than software at this point, or a combo of both I dunno
---------- Post added at 11:56 AM ---------- Previous post was at 11:55 AM ----------
PaulIvan said:
I got sick and tired of trying new ports, new PCs and new usb cables so I had mine sent away to samsung for repairs. The problem was just too complex for me.
Thank you for help anyway.
Click to expand...
Click to collapse
How much did it cost you?? I have that counter thing on 1 when I rooted it so I won't be covered under warranty....
I'm using my nexus s which is great, I love 4.2.2 its just really slow since it is 2.5 years old at this point.
And the green bar just kept sitting there going nowhere...
I'm trying to do an older firmware factory sim unlock, but first I gotta get the older firmware on my phone...
I downloaded this http://androidromupdate.com/2012/11...y-note-2-sgh-i317-original-factory-stock-rom/ and it was the culprit that failed halfway through, I click start again thinking it'd try and start the flash over again....
I done one that was just simply named I317UCALJ2_I317ATTALJ2_ATT.zip and it flashed successfully rebooted then booted in the default recovery for a second then rebooted loaded the samsung logo then the at&t screen then it sat and sat at the second samsung logo...
Should I take the battery out and try to enter download mode again or...
Factory reset
How in Kies through recovery mode? Took the battery out now I get a yellow exclamation triangle telling me to do it there. But everytime I try to press power, home and up key it gives me this screen.
Funny how on my first note 2 I was able to do all this no problem second time around I get stuck...
ID say odin didn't flash it correctly I had an issue like this on my s2 it wouldn't even boot to the Samsung logo just keep telling me to use kies recovery every time it got stuck I rebooted it closed odin pulled battery then reentered download mode and tried again not sure if it will help or hurt but it took me 20 tries to get it to fully flash and reboot into os
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Been trying to get into any mode but it keeps going back to this screen with a phone on the left side yellow exclamation sign in the middle and a pc on the right side... No sooner than it powers on it goes straight to this screen.
n1nj4Lo said:
Been trying to get into any mode but it keeps going back to this screen with a phone on the left side yellow exclamation sign in the middle and a pc on the right side... No sooner than it powers on it goes straight to this screen.
Click to expand...
Click to collapse
Will it connect to odin from this screen ? its basically download mode u should be able to flash from it
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
oddspec said:
Will it connect to odin from this screen ? its basically download mode u should be able to flash from it
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yup it connected to that, I guess go through with the one rom that did work and hope it loads up, then onto sim unlocking it then installing something like PCR, TWRP or CWM
n1nj4Lo said:
Yup it connected to that, I guess go through with the one rom that did work and hope it loads up, then onto sim unlocking it then installing something like PCR, TWRP or CWM
Click to expand...
Click to collapse
OK good luck sorry can't be of more help never owned a note so no clue about what to flash hope u get it working
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
oddspec said:
OK good luck sorry can't be of more help never owned a note so no clue about what to flash hope u get it working
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Ran into another problem went to reflash the rom and it just sits there on Get PIT for mapping... Doing nothing at all been sitting there for a minute or two now.
Okay now it said Complete(Write) operation failed
This is what all I get
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and so then of course after this if I unplug it and the battery it's back to the same screen again....
No one has anything, should I select something else? I'm lost...
Finally!! After several tries I got it to go into download mode and successfully installed the older firmware then sim unlocked and then installed CleanROM...
n1nj4Lo said:
Finally!! After several tries I got it to go into download mode and successfully installed the older firmware then sim unlocked and then installed CleanROM...
Click to expand...
Click to collapse
Glad to hear it
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Late to the party. ...sorry bro...
Your odd screen was Odin limp mode. .
If it happens again. ...
Push and hold your Odin button sequence and wait until it vibrates 3 times.
Then you'll be in Odin mode again for flashing.
BTW....you were "this" close to bricked. ...
That sequence reboots Odin. ...and is the last attempt before JTAG....LOL
NICE SAVE !!....g
gregsarg said:
Late to the party. ...sorry bro...
Your odd screen was Odin limp mode. .
If it happens again. ...
Push and hold your Odin button sequence and wait until it vibrates 3 times.
Then you'll be in Odin mode again for flashing.
BTW....you were "this" close to bricked. ...
That sequence reboots Odin. ...and is the last attempt before JTAG....LOL
NICE SAVE !!....g
Click to expand...
Click to collapse
I gave up for an hour then before I went to bed I decided to give it one more last try... I think my problem before was I was plugging the phone in and then trying to enter download mode, so I tried it with the phone unplugged. Somethings automatically power the phone on into a new state when turned off. I'm glad I tried once more, I was looking up stuff about "Yellow Triangle of Death" and youtube tutes and all kinds of stuff.
n1nj4Lo said:
I gave up for an hour then before I went to bed I decided to give it one more last try... I think my problem before was I was plugging the phone in and then trying to enter download mode, so I tried it with the phone unplugged. Somethings automatically power the phone on into a new state when turned off. I'm glad I tried once more, I was looking up stuff about "Yellow Triangle of Death" and youtube tutes and all kinds of stuff.
Click to expand...
Click to collapse
No Offence, i would recomend stop messing with your phone....lol
you have posted all sorts of issues that i have seen, even before your phone got swiped( bummer )
Now that you have it with cleanRom on it.....LEAVE IT BE BRUH<<<<<
the2rrell said:
No Offence, i would recomend stop messing with your phone....lol
you have posted all sorts of issues that i have seen, even before your phone got swiped( bummer )
Now that you have it with cleanRom on it.....LEAVE IT BE BRUH<<<<<
Click to expand...
Click to collapse
I really have no problem flashing rom's the second hardest thing I ran into was flashing a custom recovery to it but changing usb ports fixed that...I don't plan on doing the t-mobile aws qcn on it till I get a chance to fully test it out without the hack... Now that I've got a custom recovery I'm all set...
Odin flashing is a bit more complex than flashing through custom recovery. I ran into this problem probably because of a bad rom download for Odin...
the2rrell said:
No Offence, i would recomend stop messing with your phone....lol
you have posted all sorts of issues that i have seen, even before your phone got swiped( bummer )
Now that you have it with cleanRom on it.....LEAVE IT BE BRUH<<<<<
Click to expand...
Click to collapse
^^^This! None of these issues should have come if you simply follow the directions.
Sent from my CLEAN Note ll