Related
Dear Folks at XDA,
I would like to ask for you help with my HTC Touch Pro 2. I recently tried to update it to the new AthineOS CHome TF3D WM6.5 Manila ROM v 1.0 and unfortunately I failed.
The problem is that my phone now freezes at the black startup screen with the Touch Pro 2 logo and the red codes at the bottom.
I've flashed the ROM several times before and never got this issue.
Due to the fact that the phone doesn't finish the boot-up and I thus I can't get ActiveSync I'm afraid I messed up my phone for ever.
Please someone tell me I got a way out of this, I'd appreciate it very much.
Greetz,
SjonSjon
umm.... I don't think you can change the firmware just yet on the CDMA version of the phone... if you used a HardSPL that's available in the Rhodium forums then you probably used a GSM specific ROM on your CDMA phone... not sure what to tell you other than making sure you read the CDMA forum before trying something so risky. Best solution, unless someone knows how fix your phone in it's current state, is to toss it under your car and run it over and try to cash in on the insurance.
Problem solved!
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
I am glad you have recovered the beautiful device; and thanks for sharing a working solution.
sjonsjon said:
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
Click to expand...
Click to collapse
Good job!
big thanks for solution.
You just saved my life!!!
Don't get our hopes up! This is the wrong forum. CDMA TP2s can't be flashed at all yet.
This was a life saver post so a quick bump for anyone that needs it.
I unlocked my CDMA phone, installed a few roms -- decided to go back to my stock rom default (which was Telus) -- reinstalled and bam -- bricked.
Well, technically it's not a brick if you can get back into the bootloader to reflash. So no worries everyone. If everyone reads instructions well enough we should hopefully see zero "real" bricks. Or at most, just enough to only build bbq pit rather than a house.
I think my phone is truly bricked
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
my cdma is rebooting endlessley i reflashed stock rom and evorything. it seriously dosnt want to work. its most sadness... i am cashing in on the insurence. but they are going to send me a refurb..
spend 600$ on a phone got inurnce i hope the used one dosnt fail me.
Esazi said:
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
Click to expand...
Click to collapse
I did the same exact thing to mt TP2. Same outcome.
We have to learn somehow....
That stinks man. If you did, then your phone is truly bricked. You are going to have to get a replacement or switch to another phone because there is nothing you can do to get it going again. I tried everything possible and eventually just ordered a replacement. I have it now and it's working beautifully, but needless to say I am a little scared away from any more unlocking or flashing for a while.
If you read carefully you dont have to be scared of flashing
I was a noob some time ago but before doing anything I took care of reading and understanding before doing nothing.
lesson learned
By now I have flashed more than 60 times on 3 diferent HTC devices and all were a succes
Hope you get your TP2 working again!
I hope I can get there
Someday I hope to be a flashing expert, but until then I will take it slow and read carefully. Thanks for your encouragement. When I actually get money to pay for the unlock for my TP2, I will let you know how flashing goes.
How do you keep the phone in bootloader? Mine goes right to the press volume instuction screen. Other than that I'm stuck on the black name screen,also my usb will not register in device manager. This was my first try at flashing.
gadgetgirl28 said:
You just saved my life!!!
Click to expand...
Click to collapse
Holy hell, you're not lying. Thanks for coming back to post your solution!
This post saved me at least a few hours of frustration and ever worsening decision making.
So it's totally true???
this situation hasn't solution;
I was unlocking my phone (the HTC Touch Pro 2 <SPRINT>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, AND PLEASE somebody tell me , that it can be save it
;9
please help
i have the same problem. is there a way to save my phone?
Hello all. i am noob. i just got the infuse last night. used the 010 hex editor to get the unlock code for the phone. i also used that 1click root program. the problem i am facing is that after i did all of this my dial pad is all messed up. the bottom buttons (send key, voicemail key etc) are cut off about half way. its almost as if its a screen resolution problem. was hoping someone has an answer to this better than what att told me which is i need to get a new phone, i really hope thats not the case. please help!
GTG's Ultimate Unbrick will put your phone back to stock.
Then use SuperOneClick to root and I used InfuseRootUnlock_v4, to get my Unlock code.
Any guaruntees it will work? i will try this. and the unlocker you speak of i tried using but kept getting an error message and it wouldnt provide me the unlock code. i guess i could punch in the same one i have written down? I appreciate the help, thankyou.
I don't trust att. My dsl was down, I told them that I knew of three others that were also down.
She had me unplug my dsl modem, then informed me that ghe modem was bad because she couldn't access it.
She then proceeded to try and sell me a new modem. I refused of course, knowing that it was them and not me.
So, no guarantees, but that's what I'd do.
Cranky...
ok. So, i turned the phone off. took out the battery, gave it a second, popped the battery back in, held down both volume buttons while doing so plugged in the usb cable, nothing shows up in the COM line on Oden3.
Sigh what to do now?
Is there any other way I can get the phone back to stock everything?
By the way, if it helps, when i rooted the phone I did NOT install any custom roms, i left it the way it was.
Thankyou for all the help you have been giving me so far.
and Odin recognizes it when i have the phone on and plug it into my computer.
When i boot into down load mode, My computer says that it does not recognize the device? which is weird.
I have also installed Kies
Okay, sorry to be posting endless amounts of posts but i just found something out. This phone must have already been rooted and someone must have already installed a custom rom. i looked at the phone settings and it says its running on "Infused". Now, going into clockworkmod and then into download roms, then to the gtg465x, in BIG BOLD letters it says "WARNING: DO NOT TRY TO INSTALL YOURSELF! FOLLOW INSTRUCTIONS POSTED ON XDA" - Infused v2.2.3
Which is exactly what rom i am running on.
My guess is, is that some "genius" decided not to pay attention to that and follow the directions and screwed it all up. WHICH was not me. Hence, i have not installed a custom rom on this phone.
So back to step one I guess. I sincerely apologize for this, I really do appreciate your help.
Could I install another custom rom such as CM7? Maybe that will fix the dialer issue?
FIXED
okay so i fixed it. All i did was re,download the rom. did both wipes, (didnt do backup, already had one) let it install the rom again, back to normal. Finally.
Thankyou for your cooperation though!
Glad to hear
Cranky...
same problem
chuckles_prs said:
Hello all. i am noob. i just got the infuse last night. used the 010 hex editor to get the unlock code for the phone. i also used that 1click root program. the problem i am facing is that after i did all of this my dial pad is all messed up. the bottom buttons (send key, voicemail key etc) are cut off about half way. its almost as if its a screen resolution problem. was hoping someone has an answer to this better than what att told me which is i need to get a new phone, i really hope thats not the case. please help!
Click to expand...
Click to collapse
im having same problem on tmobile note 3 running dompop v5.1 i cant find a solution have you yet.
OK, My first attempt at messing with the firmware on an Android phone resulted in dismal failure and a dead phone..
Here's the scenario as events unfolded..
Bought an unlocked Galaxy S 4G
Trying to connect my phone to my PC resulted in dismal failure, wondered if it might be a dodgy firmware someone had installed.
*#2663# to update the TSP firmware. This just hung on the updating screen. Eventually the battery gave out. (Don't ask me why I was updating the Touch Screen Panel Firmware, I don't know.. I was fiddling. )
Recharged the battery and rebooted the phone.. Menu and Back buttons on touch pannel light but don't work.
Searched this forum and many others, seems to be a common problem but no clues as to how to resolve.
So I downloaded Odin 307 and the USB drivers, put phone in download mode, installed the following via Odin
CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar
SGH-T959V-CSC-TMB-VIBRANTP.tar
T959VUVKG4-Phone-CL1037720.tar
Worked fine, but didn't fix the issue with the TSP.
Somewhere I read that maybe it was partition corruption, so I decided to repartition. Ticked the "Repartition" box and used Hawk_Sidekick_VibrantPlus_831.pit (All four of these came as a package I found linked to on this site somewhere.) Odin said it was ok, but now I can't even power the phone on. Screen stays blank. Computer does not recognise USB device. Odin doesn't see it. It seems to be dead.
So.. Is there a rescue remedy from this scenario, or do I use this piece of glass and electronics to wedge my door open?
Please help I'm not going to pretend I knew what I was doing, but I'd like to unbrick this thing so I can at least make phone calls on it and send emails to people saying what a plonker I've been..
Thanks. :crying:
Do you have a T959V or T959 ?
Check under your battery.
Sent from my SGH-T959V using xda premium
T959V
No, I've not tried that. I'll give it a go.
The Heimdall One Click has saved my phone quite a few times, it's simple and effective! Let us know how it goes!
Sent from my Illūsîøn'd Galaxy S³
Ok, so I managed to get it into Download mode and reflashed it in Odin. I'm going to have a go with "oneclick" and see what happens, but at this point the only outstanding thing to fix is the TSP, which is still kaput. (Maybe one click will fix that) I've searched and searched on this forum, there's a whole bunch of dead threads where people have killed their TSP, and no resulting fixes posted. If anyone has any ideas, its would be great if you could post them, because at the moment, "menu" and "back" are still U/S.
Thanks for your help so far. If I get a solution, I'll post it here, I hate abandoned threads where people leech solutions to their probems and don't give feedback.
OK, So I tried this : http://forum.xda-developers.com/showpost.php?p=23121150&postcount=12&nocache=1&z=6720291850525859
No luck..
Next thing to try is an older version of the O/S, apparently if I put on then it downgrades one of the firmware, and running the update again fixes the issue. (On can only hope.. Now I gotta go see if I can find an older version of the OS and try this http://forum.xda-developers.com/showpost.php?p=21987511&postcount=9
:fingers-crossed:
Oh well.. On the plus side, I bought this little cheap phone to play around and learn on.. I seem to be doing just that. :cyclops:
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
eKulzz said:
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
Click to expand...
Click to collapse
You can root it and then try installing agni kennel from recovery
Sent from my GT-P3100 using Tapatalk
eKulzz said:
I'm not even kidding, everything takes a good 10 seconds to open. I can't scroll through settings because it takes 3 seconds to register my swipe.
It's a family members tablet and it has never been rooted, or flashed any custom ROMs. The 4.2.2 update came from Samsung and ever since then they've been complaining to me about how slow it is.
I'm having the same problem when trying to clear the cache through recovery - the dead android and 'error'!
I do NOT want to flash a new ROM because it involves resetting all apps and settings back to how they used to be. The owner hardly has any idea how to use it, so any changes will just freak them out.
Is there anything I can do to fix this thing?
Click to expand...
Click to collapse
Root it and install an app called seeder .
It makes 4.2.2 super fast ..
Greetings;
Either it was a terrible custom Rom, or you didn't flash it properly.
If you wan't it to work properly consider that you will have to Backup your Applications; their Data and your Contacts as well if they are not syncronized with your Gmail Account.
Perform a "Clean Flash" whenever you Flash a Rom to prevent Issues, and use Odin (for PC - Never Odin Mobile) for such "Clean Flash).
Also Consider Researching Before Doing any Operation you are not familiar with.
What you should try:
0) Backup your Apps & Data;
1) Boot your Device under Recovery;
2) Under Recovery:
- Perform Factory Reset
- Clean Cache
- Reboot into Download Mode
3) Open Odin, under PDA Load you Stock Rom [MD5 file] (to revert your Device Settings to Stock).
4) Under Odin: Considering your Device is Recognized, Press Start.
Do NOT Disconnect USB Cable until Odin Displays "PASS" Message.
5) Reboot into " Download Mode " to Flash ClockWorkMod Recovery or CF-Root (or your Fav. Recovery).
6) Once Completed, Boot your Device into Recovery and Perform " Factory Reset ".
7) Test your System.
Let me know how it went.
Best Regards,
Richard
Any Joy
eKulzz: Did you have any success with the above suggestions? I am in exactly the same boat. I inherited the device (Galaxy Tab 2 10.1 5113 16gig) from a family member. I am not really sure precisely when it started to suck so bad....I am assuming, based on the internet posts, that it happened as a result of the 4.2.2 upgrade. It is taking literally minutes in some cases to load a web page. Flipboard is particularly bad. I have cleared cache, uninstalled or disabled every app the tablet will allow, done a full revert to factory, and nothing works. My wifi throughput goes down to miniscule rates (5, 10 , 15 kbps), although once in a while, for larger objects it will jump up to 5 or 10 mbps....so I know it can do it!). I have done IP traces, thinking it might be my internet provider, but the delays are after the TCP/IP response is returned. It seems to peg the CPU and wander off for 10 or so seconds, and then proceed to do the next TCP/IP request.......so if a page has lots of content, it can take minutes to load.
I am at the point that I either throw it away, try to revert to the original android version the tab was delivered with, or possibly go the other way and instally cyanogenmod, in which case it would be interesting to know the best version of android to install on this device, based on other people's experiences.
It is so amazing that this can happen....and it doesn't seem like an isolated case....the vendor just seems to have effectively bricked a major part of their customer base, and won't admit or do anything about it. You can be sure my next purchase will not be Samsung!
However, in Samsung's defence, almost the same thing happened with my Nexus 7 2012 WIFI tablet. The android 5.1 upgrade has made it almost as bad as the Samsung. I wasted days following threads and screwing around, but only achieved minor gains...it is still not really usable. Again, no mea culpa from Google.... I find it amusing that there is such furore when a new release of android comes out and there is such outrage if peoples devices are not supported, or not upgraded fast enough. My point of view now is that I don't want to see an upgrade on any device I have that is working acceptably.....I think there is such pressure from users for upgrades that the vendors are not testing enough and not asking themselves if the upgrade is actually improving usability for the device....
Rick
Have you tried downgrading?
Go sammobile website, Download the Rom version for your device, and follow the procedures i wrote previously.
(Dont forget to erase cache(s)).
Also check for flash counter. You may need to reset it.
Let me know how it went - with detailed info.
Best regards;
Richard
Tried Downgrade
rgxHost said:
Have you tried downgrading?
Go sammobile website, Download the Rom version for your device, and follow the procedures i wrote previously.
(Dont forget to erase cache(s)).
Also check for flash counter. You may need to reset it.
Let me know how it went - with detailed info.
Best regards;
Richard
Click to expand...
Click to collapse
I gave it a try. Got stymied with the USB drivers. I installed them, but the PC (windows 10) will not recognize the USB device, so Odin does not see the tablet.
I got the drivers from the Samsung web site, and also tried another set, but no luck. I am pretty sure they are the correct drivers...., and were installed successfully, so I am not sure whether it is a Windows 10 thing or a driver problem. The PC sees the device when you plug it in and remove it, but reports it as an unrecognized device. I tried re-booting the PC, just in case.
Anyway....it has pretty well stopped me in my tracks.
Rick
Update
Rickster22 said:
I gave it a try. Got stymied with the USB drivers. I installed them, but the PC (windows 10) will not recognize the USB device, so Odin does not see the tablet.
I got the drivers from the Samsung web site, and also tried another set, but no luck. I am pretty sure they are the correct drivers...., and were installed successfully, so I am not sure whether it is a Windows 10 thing or a driver problem. The PC sees the device when you plug it in and remove it, but reports it as an unrecognized device. I tried re-booting the PC, just in case.
Anyway....it has pretty well stopped me in my tracks.
Rick
Click to expand...
Click to collapse
Update: Tried installing the USB drivers from Samsung on a 32 bit windows XP netbook I had lying about. Same result. The tablet is reported by the OS as an "unrecognized device" when I plug it in, and Odin does not see it.
I guess it could be my cable....but it is the only one I have, and since Samsung uses a non standard cable, I would have to buy a new one to find out. I definitely am not going to do that....talk about good money after bad. I have spent about 10 hours on this.
Interestingly, I ran into a guy at a party last night that is experiencing the same slowness on a galaxy tab 2 7" . Seems too coincidental! We were wondering if it could be related to slow SD ram with bad memory locations degrading over time, and possibly a change in android 4.2.2 garbage collection or memory management.
I think the outcome of this is that Samsung is an undependable vendor, that I don't want to invest any more time or money in. No future product I purchase will be from them.
Rickster22 said:
Update: Tried installing the USB drivers from Samsung on a 32 bit windows XP netbook I had lying about. Same result. The tablet is reported by the OS as an "unrecognized device" when I plug it in, and Odin does not see it.
I guess it could be my cable....but it is the only one I have, and since Samsung uses a non standard cable, I would have to buy a new one to find out. I definitely am not going to do that....talk about good money after bad. I have spent about 10 hours on this.
Interestingly, I ran into a guy at a party last night that is experiencing the same slowness on a galaxy tab 2 7" . Seems too coincidental! We were wondering if it could be related to slow SD ram with bad memory locations degrading over time, and possibly a change in android 4.2.2 garbage collection or memory management.
I think the outcome of this is that Samsung is an undependable vendor, that I don't want to invest any more time or money in. No future product I purchase will be from them.
Click to expand...
Click to collapse
Your guess is right, that's the cable issue, I have changed 3 cables already for my tab 2. I bought a cheap USB cable, and that worked same like the original one.(not suggesting you do the same)
Now, about the slowness, it's an every user issue who are on stock rom, yes, Samsung messed up things with ics/jb and a cheap emmc, but you can stop it before the bug hits the stock user and make the tab a hard bricked tab. few users have reported this already. they were on stock, never went custom, still their devices started slowing and eventually bricked or worse, rendered a read only device.
it's that time already, when I would want to see every tab user who are running on stock to take their tabs in their hands and start flashing the custom rom before the tab hits the brick. Good Luck
billysam said:
Your guess is right, that's the cable issue, I have changed 3 cables already for my tab 2. I bought a cheap USB cable, and that worked same like the original one.(not suggesting you do the same)
Now, about the slowness, it's an every user issue who are on stock rom, yes, Samsung messed up things with ics/jb and a cheap emmc, but you can stop it before the bug hits the stock user and make the tab a hard bricked tab. few users have reported this already. they were on stock, never went custom, still their devices started slowing and eventually bricked or worse, rendered a read only device.
it's that time already, when I would want to see every tab user who are running on stock to take their tabs in their hands and start flashing the custom rom before the tab hits the brick. Good Luck
Click to expand...
Click to collapse
Thanks very much for your feedback....nice to know I am not alone, and not losing it! If it is happening to all Samsung Tab 2 users, and the product is basically destined to become useless after a few years of use, and Samsung did not warn users of this limitation when they purchased.....seems like the kind of thing class actions are made of!
As a newbie, I would like to clarify your comments a bit to make sure I end up doing the appropriate thing. When you say that every Tab user should start flashing the custom ROM, I assume you are not talking about the Samsung provided ROMS for 4.1.1 (P5113UECLK7_P5113XACCLK7_XAC) or an updated Samsung 4.2.2. It sounds like doing that will not resolve the issue. Are you talking about Cyanogenmod? and if so, what version of Cyanogenmod and Android OS would be appropriate? .........I wouldn't mind giving it one more kick at the cat, if someone knowledgeable says there is a little glimmer of light at the end of the tunnel!
Thanks for your assist!
Rick
Rickster22 said:
Thanks very much for your feedback....nice to know I am not alone, and not losing it! If it is happening to all Samsung Tab 2 users, and the product is basically destined to become useless after a few years of use, and Samsung did not warn users of this limitation when they purchased.....seems like the kind of thing class actions are made of!
As a newbie, I would like to clarify your comments a bit to make sure I end up doing the appropriate thing. When you say that every Tab user should start flashing the custom ROM, I assume you are not talking about the Samsung provided ROMS for 4.1.1 (P5113UECLK7_P5113XACCLK7_XAC) or an updated Samsung 4.2.2. It sounds like doing that will not resolve the issue. Are you talking about Cyanogenmod? and if so, what version of Cyanogenmod and Android OS would be appropriate? .........I wouldn't mind giving it one more kick at the cat, if someone knowledgeable says there is a little glimmer of light at the end of the tunnel!
Thanks for your assist!
Rick
Click to expand...
Click to collapse
Yes, I meant Custom ROM(cynogenmod) and not stock official builds as they have fixed the trim related problem present with the old stock official ROMs, that's causing the slow downs and eventually causing the tab emmc card to die.
Check here for this emmc bug
http://wiki.cyanogenmod.org/w/EMMC_Bugs
that's one reason, cheap emmc is second (although both users have been hit with the emmc bug but c'mon a person who had never rooted or flashed a custom ROM on his tab ever got hit with this was very disappointing for stock users)
If you check other threads in help and troubleshoot you will see numerous users on stock having more brick issues than the custom ROM users. I have been here from long and have been watching over on all the issues. both have equal share of risks.
See this case here too
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
So, if you're planning to choose custom ROMs, take a tour of the General sections for guides and Android development section for ROMS.
Most of the ROMs of our TAB 2 developer Android-Andi, CCD and tuxafgmur are fine and near stable(with updates) (don't go below KK versions)
I have originally a Tmobile Galaxy S6 that I had jailbroken and now then they blocked my IMEI. I paid some guy to fix that issue and that was months ago, I don't think that is even related I just want anyone to know the history of the phone because I don't know maybe it is apart of my issue. So yesterday Im on my phone just playing a game and the S6 freezes up and its happened once or twice where i would push the home and power and eventually it would start working. So it freezes and then shuts off and goes to the Samsung Galaxy S6 Powered by android screen and will not get off that screen at all!! So I do some searching around, long story short I get to the point where I downloaded Odin 3.10.6 and I download the firmware for my phone which I found by putting it in download mode or odin mode it said at the top. It says product name SM-G920T. So I download the firmware that goes with that put it in Odin it goes to success and all looks good and the video I was watching showing how to do this showed the phone go back to the samsung screen and then start working pretty much well mine just went right back to the samsung screen and that's all it does. I downloaded the newest odin, with the newest samsung usb drive installed with trying different firmwares that I downloaded that were supposed to be for SM-G920T. So I'm at the point of smashing this P.O.S and just buying a new one. Is anyone able to help or tell me what I'm doing wrong or something, anything.
Can you post a screenshot of your ODIN settings - you might be flashing it to a wrong partition.
vordhosbnbg said:
Can you post a screenshot of your ODIN settings - you might be flashing it to a wrong partition.
Click to expand...
Click to collapse
Could you be more specific on where you're talking about? Tell me what you want me to do exactly if you can to so you get exactly what you want to see
charliehuron said:
Could you be more specific on where you're talking about? Tell me what you want me to do exactly if you can to so you get exactly what you want to see
Click to expand...
Click to collapse
You've said you used ODIN to flash the SW to your phone. ODIN has a lot of checkboxes, buttons, etc. I personally have bricked a phone just by clicking the wrong checkbox, so I just thought your problem could be related. So to be specific - could you post a screenshot of the ODIN you used and describe what kind of options you selected, what buttons you pressed, etc.