Hello
i'm in the situation that i have read several times in the forum, but unlike those cases,
i dont get to fix the point.
I got a Samsung Ace S5830i. No root, no custom rom/fw, all original.
The phone has been used for 2 years and recently it was often disconnected from the mobile network. Until some days ago, i was not able to restart it.
When i try to switch on, it was stuck on Samsung logo screen.
After that, i have tried to start it in Recovery Mode (Vol - Home and Power on keys).
I have tried all options in that mode, but i never understood ih those actions were completed successfully. Anyway, any choice fixed my problem.
So i try to play with Kies, Odin and stock firmware from Sammobile.com.
Odin recognized the phone in download mode, but i did not get to flash.
Sometines Odin message was Failed, sometimes it was stuck at "setup configuration" message.
I have changed PC, USB port, different Odin version, different FW, but every time the same results.
Im now thinking that the Flash EEPROm is damaged. Is there any way to check its integrity?
Please help me, because i would avoid to change the phone.
Thank you very much
allora
same problem
allora80 said:
Hello
i'm in the situation that i have read several times in the forum, but unlike those cases,
i dont get to fix the point.
I got a Samsung Ace S5830i. No root, no custom rom/fw, all original.
The phone has been used for 2 years and recently it was often disconnected from the mobile network. Until some days ago, i was not able to restart it.
When i try to switch on, it was stuck on Samsung logo screen.
After that, i have tried to start it in Recovery Mode (Vol - Home and Power on keys).
I have tried all options in that mode, but i never understood ih those actions were completed successfully. Anyway, any choice fixed my problem.
So i try to play with Kies, Odin and stock firmware from Sammobile.com.
Odin recognized the phone in download mode, but i did not get to flash.
Sometines Odin message was Failed, sometimes it was stuck at "setup configuration" message.
I have changed PC, USB port, different Odin version, different FW, but every time the same results.
Im now thinking that the Flash EEPROm is damaged. Is there any way to check its integrity?
Please help me, because i would avoid to change the phone.
Thank you very much
allora
Click to expand...
Click to collapse
Hello, same happened to my wife's phone. With exactly same symptoms. I tried all you have described with no luck.
If you find some solution, let me know, I will do the same
Jerryzak73
jerryzak73 said:
Hello, same happened to my wife's phone. With exactly same symptoms. I tried all you have described with no luck.
If you find some solution, let me know, I will do the same
Jerryzak73
Click to expand...
Click to collapse
Jerryzak73,
bad news.
Yesterday i have got to flash the original firmware with Odin 3.07.
I was very happy to see the completion of the flashing process (100%, successfull), but ...
when the phone restarted, it was again stuck at boot with message:
-- Appling Muti-CSC --
i dont't what this message means and ask to the forum board some help,
to definetely assert that my phone is broken hardware and i have to trash it!
:crying:
fixed
Allora,
I gave up on trying to fix it myself and gave it to a mobile shop. they reinstalled the phone to factory settings for 10EUR, so far so good.
BR, jerryzak73
Related
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
Howdy, DBNP,
The Exhibit II is pretty much unbrickable...you won't need to resort to esoterica like jtag
The guide in the Exhibit II Wiki usually works out well. I'd try booting into stock recovery, doing a data wipe, then install stock with Odin. The Wiki has the links to the files you need. BTW, I didn't write the Odin portion @ the wiki; I just hosted required files when the links went stale.
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Once you're back up and running first thing you should do is install Clockworkmod. HTH, & good luck.
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
deathbenotproud said:
I cannot get my phone to get into recovery mode, though. if I press volume+up, the phone simply displays the firmware error message. thus, I cannot do a data wipe.
Click to expand...
Click to collapse
Sorry if this is redundant, but this was with:
Easy way to start recovery
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
This has never failed for me. IDK, Perhaps your earlier Odin try wiped the recover partition. Can you get into Download mode? (hold Power-on Vol-Down)
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
deathbenotproud said:
I can enter download mode, but I cannot enter recovery mode. volume down gets me into download, while up gets me the error message. I cannot get to that menu anymore.
Click to expand...
Click to collapse
Are you saying that you get an error when you press Vol-Up at the initial "Warning!" "A custom OS can cause..." screen, the initial download mode screen?
when I press and hold the vol-up sequence, it takes me to the initial error of "firmware upgrade has encountered an issue..."
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
deathbenotproud said:
when I press and hold the vol-up sequence, it takes me to the menu where it says custom OS etc., press up to continue, down to cancel (restart phone).
Click to expand...
Click to collapse
And when you press Vol-Up at this screen what happens?
it takes me to odin mode/download mode.
deathbenotproud said:
it takes me to odin mode/download mode.
Click to expand...
Click to collapse
OK, that's good. That tells us that your exhibit2's /dev/block/mmcblk0p5 partition is undamaged. AFAIK Odin when properly used, can flash a new rom to your phone. Please try again, following the instructions in the wiki, reading carefully, downloading any files that you need, if you don't have them. Please walk through the wiki procedure to reflash stock from Odin, this procedure has worked for many,many people. Keep careful notes, you may be an edge case for some reason.
I'm posting links to this thread in the discussion threads that we use, since we're not allowed a forum. These threads get the most attention.
Exhibit II 4g discussion HERE
Exhibit II 4g dev thread HERE
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
deathbenotproud said:
yeah, I have tried doing that myself, as well as my friend who is rather skilled with android devices. he tried that all himself today, as well as attempting add. nothing worked.
Click to expand...
Click to collapse
I think you and your friend did it wrong. You should try again, following the wiki carefully.
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
deathbenotproud said:
we re-did it this morning step-by-step with no new results. we tried three times.
odin does its thing successfully, then when it goes to reboot, instead of going into recovery mod, it just goes to the firmware upgrade issue message.
Click to expand...
Click to collapse
Sorry to hear it. If Odin won't fix your phone and you've only had it a few weeks, I'd return it. I've linked your thread to our discussion threads, perhaps someone else has an idea.
that's the issue. because I have tried to flash it via odin, they're saying they won't take it because of the firmware upgrade error that keeps coming up. :/
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
deathbenotproud said:
because they won't take it, and the normal flashing to stock method isn't working, what do you think I should do next?
Click to expand...
Click to collapse
I don't know who "they" are, but the chances of anyone at a T-Mob store or a Walmart knowing you touched your phone with Odin or even what Odin is are practically nil. "It's three weeks old, I turned it on and it doesn't work. Gimmie my replacement."
Or seek out a repair service to reflash your phone.
all right, i'll take it back and get a different rep. thanks for your help, though
deathbenotproud said:
all right, i'll take it back and get a different rep. thanks for your help, though
Click to expand...
Click to collapse
I'm sorry we didn't resolve the problem. Better luck next time!
deathbenotproud said:
hello xda. been browsing for a couple weeks, but finally registered today.
I have run into a problem I would like to try and solve without having to go through my insurance or carrier. my phone bricked itself after only 16 days, with 0 modifications on it. it was factory stock still. let me describe what happened, and what I did:
1st problem: I was using my online banking app (reputable bank), when the app minimized to the main screen; however, nothing OS related loaded. the phone just froze. only the wallpaper was visible. I tried powering it down, but it wasn't responding, so I pulled the battery, and put it back in. I powered on the phone, it loaded the SAMSUNG screen, then went to the Exhibit II 4G page, but then it stopped. it failed to load past the Exhibit II splash screen. no matter what I did, it stayed there. I googled for hours, trying various things, until I finally found this site with a stock rom setup.
2nd problem: I followed jocala's guide for flashing it, using Odin 4.43, and after it finished flashing, I got a "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." so now I have been googling this issue, and I cannot seem to find anything on how to fix it. I don't understand how my phone can just brick itself while using a banking app that i'd been using since I got the phone.
any help would be appreciated
also, if this isn't the forum for it, feel free to move it. this just looked the most appropriate seeing as there wasn't a board for the phone specifically.
Click to expand...
Click to collapse
go into recovery and do a factory reset then reboot from recovery.
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying
Hello All!
My first post here, even though I have long been a lurker. I hope I'm posting in the right place. If not, apologies, and Mods - please redirect me, and I shall re-post in the correct place.
Phone: SAMSUNG GALAXY S3 GT-I9300 International version
Last known installed/running OS: Official SAMSUNG JB ROM (Unsure WHICH version) after having run on CM 4.4 for a couple of weeks.
PROBLEM:
a few months after going back to stock, Phone suddenly developed issues of random reboots. These would happen at any point in time, with no predictability whatsoever. One fine day, it rebooted, and wouldn't get past the Samsung splash screen. Pulling the battery and trying to restart phone resulted in the same stuck at Samsung logo issue.
Left the phone alone for a couple of months after this as I had a spare, but finally decided to try and revive the S3.
Phone does not charge when connected to charger. At least, it shows no visible signs of it. It DOES, however, try booting itself when plugged in, but gets stuck on the first screen of ODIN Download mode, instead of the Samsung logo splash screen as it used to earlier. Also note that this screen it gets stuck on is a pixellated screen, not the clear normally seen screen when entering ODIN mode.
The Vol UP, Home and power button combo brings me to this very same screen, there is no recovery menu to be seen, as would be normally. The Vol DOWN, Home and power button combo brings me to the regular clear ODIN mode as usual.
The headings at this screen read:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I have read through most posts regarding similar issues on XDA as well as other forums, and tried flashing stock firmwares (single AND multiple part ones) through ODIN, with no success. The error i always get is as in the attached screen captures.
I've tried ALL versions of ODIN, and many PIT files. All were failures.
So, is this a dead for all purposes phone, or do I still have hope since ODIN mode is still available?
I don't think USB debugging was checked before bricking, because ADB toolkits just keep waiting for phone to be detected.
All drivers are up to date and installed correctly. Kies is not installed.
Any help is welcome.
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
I have a Device here which seems to have the same or at least a similar problem, however, i got it for free from someone else to experiment with, so there is no urgent need to repeir it.
I tried flashing a pit and erasing nand, but when i start to do it, odin just gets stuck at "erasing", if i try to flash a full firmware it just hangs at "getting pit for mapping" so i assume the nand is gone for good... however, i have one more dead s3 arround that seems to have a burned cpu, probably i manage to solder over the nand or the cpu
rp158 said:
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
Click to expand...
Click to collapse
ODIN stays at "Setup Connection" without any progress. I've left it overnight a few times, just to ensure I was giving it enough time.
When the cable is pulled, it reads "there is no pit partition"
@Mohanms04: I suppose, it's hardbricked
rp158 said:
@Mohanms04: I suppose, it's hardbricked
Click to expand...
Click to collapse
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Mohanms04 said:
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Click to expand...
Click to collapse
Try this recovery firmware, if not the jtag is required.
http://forum.xda-developers.com/showpost.php?p=30087735
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Simeonico said:
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Click to expand...
Click to collapse
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Simeonico said:
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Click to expand...
Click to collapse
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The S2 doesn't vibrate when you turn it on (at least the i9100 model), but don't worry it's completely dead. No boot, no recovery, no download mode, no nothing. If I'm bored enough I might buy a new motherboard from AliExpress in the future cause they're really cheap.
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.