I had hard bricked my Infuse some time ago trying to update Android to Jelly Bean if I remember correctly. Today I tried to fix it. I followed this thread. The phone gets to the point where it reboots, but then it won't boot into Android it only boots into recovery mode. I don't know anything about flashing, but I'm guessing what I need to do is flash the stock ROM.
Could anyone help me?
thblueoval said:
i had hard bricked my infuse some time ago trying to update android to jelly bean if i remember correctly. Today i tried to fix it. i followed this thread. The phone gets to the point where it reboots, but then it won't boot into android it only boots into recovery mode. I don't know anything about flashing, but i'm guessing what i need to do is flash the stock rom.
Could anyone help me?
Click to expand...
Click to collapse
i have same problem
crizalid8 said:
i have same problem
Click to expand...
Click to collapse
You could try a back-to-stock method, using Odin.
If you are using AT&T (option D or A, depending if you want CWM or not):
http://forum.xda-developers.com/showthread.php?t=1613523
If you use i997R (Rogers):
http://forum.xda-developers.com/showthread.php?t=1193927
Instructions are in the respective threads. Hope this helps.
joel.maxuel said:
You could try a back-to-stock method, using Odin.
If you are using AT&T (option D or A, depending if you want CWM or not):
http://forum.xda-developers.com/showthread.php?t=1613523
If you use i997R (Rogers):
http://forum.xda-developers.com/showthread.php?t=1193927
Instructions are in the respective threads. Hope this helps.
Click to expand...
Click to collapse
in download mode my phone is not recognized by my PC
sorry for my bad english
crizalid8 said:
in download mode my phone is not recognized by my PC
Click to expand...
Click to collapse
Looks like you don;t have the appropriate drivers drivers installed to use download mode.
Some people use Kies to get the drivers, me I prefer ADBSetup. The package installs generic (or at least non-specific) drivers along with your standard debugging tools (adb, fastboot).
Just download the package, run as administrator, say yes to both (or at least the drivers portion), and you should be ready to go with download mode again. If you are still having problems, you may need to reboot.
Related
Hi all, after successfully flashing aeon gears boot animation with clockwork mod from this thread http://forum.xda-developers.com/showthread.php?t=1656709 I then attempted to flash the Aeonised Forrest theme also from that same thread. This was my first attempt at flash a custom theme and as far as I am aware Entropy's kernel supports custom themes? Was it wrong to use CWM to flash the theme, according to CWM after the flash things went well however after rebooting I am stuck in a boot loop. Thinking of trying one click back to stock with this http://forum.xda-developers.com/showthread.php?t=1524081 Any ideas what went wrong? Please note that Clockwork Recovery and Download mode both still work. Any suggestions how to do it the right way would be appreciated.
Thanks Much
LordKoga
LordKoga said:
Hi all, after successfully flashing aeon gears boot animation with clockwork mod from this thread http://forum.xda-developers.com/showthread.php?t=1656709 I then attempted to flash the Aeonised Forrest theme also from that same thread. This was my first attempt at flash a custom theme and as far as I am aware Entropy's kernel supports custom themes? Was it wrong to use CWM to flash the theme, according to CWM after the flash things went well however after rebooting I am stuck in a boot loop. Thinking of trying one click back to stock with this http://forum.xda-developers.com/showthread.php?t=1524081 Any ideas what went wrong? Please note that Clockwork Recovery and Download mode both still work. Any suggestions how to do it the right way would be appreciated.
Thanks Much
LordKoga
Click to expand...
Click to collapse
what rom are you on...or where?
bigjoe2675 said:
what rom are you on...or where?
Click to expand...
Click to collapse
Using stock 2.3.6 with Entropy's Daily Driver Kernel, rooted as well. Download mode starts but phone does not show up in Heimdall trying to find a solution via ODIN as my phone shows up in that at least.
LordKoga said:
Using stock 2.3.6 with Entropy's Daily Driver Kernel, rooted as well. Download mode starts but phone does not show up in Heimdall trying to find a solution via ODIN as my phone shows up in that at least.
Click to expand...
Click to collapse
Unless I missed the bus...which I do a lot, so I just walk...LOL
Evergreen Theme Theme for AEON ROM....not stock...?
do you have driver loaded on your pc?, There are drivers for Infuse on the super infuse page, see my links...
or try diff usb port or cable...or pc...
does it ask for drivers for heimdall? which those are different drivers than odin...
if you want those nice, beautiful themes that mikig make...flash Aeon, then flash the themes...kk
but the Super Infuse page has all the ROM/tools/drivers you need for the Infuse...the individual that maints that page is just a loser, but dont tell him, he is dork with an additude...ok :laugh:
see "My links" in red...go there if you need anything else for you infuse...kk
I have a copy of ODIN with a few files in it not sure if they are useful? Files are: PHONE_UCKD5.tar.md5, infuse.pit, PDA_UCKD5.tar.md5
Will any of those fix my boot loop? Flashing a theme shouldn't permanently brick me right?
LordKoga said:
I have a copy of ODIN with a few files in it not sure if they are useful? Files are: PHONE_UCKD5.tar.md5, infuse.pit, PDA_UCKD5.tar.md5
Will any of those fix my boot loop? Flashing a theme shouldn't permanently brick me right?
Click to expand...
Click to collapse
Flashing with ODIN phone shows up with the COM thingy yellow, but seems to be stalled at SetupConnection on ODIN any help???
LordKoga said:
Flashing with ODIN phone shows up with the COM thingy yellow, but seems to be stalled at SetupConnection on ODIN any help???
Click to expand...
Click to collapse
Hold the power button down for a little while. The phone may go into a screen w/ an image of Phone-!-PC. Reset Odin and restart from there. It should work then. If not, reset Odin and put the phone in download mode again.
Sent from my HTC_Flyer_P512_NA using Tapatalk 2
LordKoga said:
A good while ago I flashed my phone with the Heimdall method provided by your one click to stock thread for GB. I then rooted my phone after flashing Entropy's Daily Driver, I being rather dumb then tried to flash one of the Aeon themes with CWM http://forum.xda-developers.com/showthread.php?t=1656709 The Forest theme from that thread. My phone then decied to go into a boot loop. I am now attempting to recover with ODIN but i think it's stuck? It seems to be stuck at SetupConnection message in ODIN. I was hoping you could offer some advince on how to unbrick myself.
Thanks
LordKoga
My thread about problem
http://forum.xda-developers.com/showthread.php?t=1779146
Click to expand...
Click to collapse
Odin and heimdall uses different device recognition drivers.
I've not used Odin for over 9 months so I can't offer advice there. Jscott30 has more experience with Odin.
If you want, you can restore your phone using the heimdall 1 click uclb3 I put together.
Flash in download mode. It will restore your phone if used correctly.
If you want to try, before flashing anything else, try first booting into recovery using the three finger techniques into cwm and flash aeon or another MUF.
Recovery may still work.
qkster said:
Odin and heimdall uses different device recognition drivers.
I've not used Odin for over 9 months so I can't offer advice there. Jscott30 has more experience with Odin.
If you want, you can restore your phone using the heimdall 1 click uclb3 I put together.
Flash in download mode. It will restore your phone if used correctly.
If you want to try, before flashing anything else, try first booting into recovery using the three finger techniques into cwm and flash aeon or another MUF.
Recovery may still work.
ODIN WORKED!!!!!
Now all good Although I think my data was wiped off
However I had no custom roms on my SD to flash and could only boot in to DL mode and CWM neither were of use .
At the very least now that I'm all clear i might flash Aeon rom.
THANKS SO MUCH FOR ALL YOUR INPUT I TRUELY APPRECIATE ALL YOU AWESOME PEOPLE.
Click to expand...
Click to collapse
LordKoga said:
THANKS SO MUCH FOR ALL YOUR INPUT I TRUELY APPRECIATE ALL YOU AWESOME PEOPLE.
Click to expand...
Click to collapse
Good luck with everything. Make sure to click the "Thanks" button on everyone that helped you out.
One thing you should take away from this experience is to make sure you do a NANDROID BACKUP before flashing ANYTHING in CWM.
Learn how to get into CWM using the 3-finger method, too. It can come in handy.
Hi,
I had before the OTA for Jelly Bean an ICS unlocked and rooted.
I tried to use ShabbyPenguin to get it rooted again but now I have a broken recovery.
So not sure what do I need to get it rooted again.. Is it possible?
Thanks!
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Not sure if it is possible to flash cwm trough adb... However I will try it later today...
And yes, bootloader is still unlocked...
rustyjay said:
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Click to expand...
Click to collapse
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
hhhmmmm... no luck yet...
I tried to flash a recovery and it keeps giving me a message
<waiting for device>
After that it seems like stuck..
I read somewhere else that maybe because of the drivers, but I already tried a couple of versions 1.3.8 and 1.5.6 with the same result...
btw I'm using a Windows 7 64 bit machine...
Not sure if use a Linux machine will have any benefit...
rustyjay said:
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
Click to expand...
Click to collapse
Well...
Also tried the google usb drivers with no luck....
I guess that I will try it with some other windows/linux version later today...
Off but on topic. Describe what you call a broken a recovery please.
When I try to run the recovery it appears a dead android with a red exclamation mark on the screen....
After that it takes some time to reboot again...
albundy2010 said:
Off but on topic. Describe what you call a broken a recovery please.
Click to expand...
Click to collapse
That is stock recovery. It is not broken.
Yes I was saying it was broken because before the OTA update I had twrp as recovery, and now I can't flash any recovery
albundy2010 said:
That is stock recovery. It is not broken.
Click to expand...
Click to collapse
When you flash/install a ota your recovery gets wiped back to stock once it boots up due to the flash recovery script in the stock ROM.
Nothing is wrong with your device. Just follow a real guide on how to unlock and root. Real meaning using the SDK. Or even use one of those stupid one click crap. should not have a issue.
Guides are in the forum stickies.
Hi Guys,
Well not sure what the problem was.... maybe the drivers, maybe Win7 64 bits or I don't what...
I used a WinXP machine with the pdanet installed and it worked like charm...
I succesfully installed the recovery and root again.
Anyway... thanks for your time.
Glad to hear that.
Hi,
I am new to this forum.
My captivate is on stock firmware UCKH3 (2.3.4)
I think I've done something wrong while flashing a custom kernel.
The kernel was flashed, the phone is booting but I am unable to get into the CWM recovery. Tried button-combo and also from ROM manager but no luck. Hence I am unable to flash any roms in the forum except odin tar's!!
I would like to try ICS roms but I couldn't find odin packages.
Please help me with this issue or post a link which may help my case.
Thank You,
Pradeep Kiran
Which kernel did you flash, and what combination are you attempting?
were you able to get into recovery before .?.
I had to use ADB to get me into recovery on my i897. If you dont know what ADB is, look it up as i did.
Careful with Odin, it will brick ur phone, but no worry many ways to get unbricked. I had to make a jig. you can order one, same price either way, just if you make one check the ohms, needs to be 301k resistance.
korockinout13 said:
Which kernel did you flash, and what combination are you attempting?
Click to expand...
Click to collapse
I've used Boog kernel with CWM from this link
http://forum.xda-developers.com/showthread.php?t=1242533
Tikiflame said:
were you able to get into recovery before .?.
I had to use ADB to get me into recovery on my i897. If you dont know what ADB is, look it up as i did.
Careful with Odin, it will brick ur phone, but no worry many ways to get unbricked. I had to make a jig. you can order one, same price either way, just if you make one check the ohms, needs to be 301k resistance.
Click to expand...
Click to collapse
Well, I got I897UCKB2 firmware when I've purchased the phone,
I tried the one click executable I897UCKH3 from the stock Rom's thread and my phone got bricked!! I made a jig to put it into download mode and flashed the same package. It is working now but I've screwed up my recovery!! I am unable to get into recovery by using adb, button combo or rom manager.
krnprdp said:
Well, I got I897UCKB2 firmware when I've purchased the phone,
I tried the one click executable I897UCKH3 from the stock Rom's thread and my phone got bricked!! I made a jig to put it into download mode and flashed the same package. It is working now but I've screwed up my recovery!! I am unable to get into recovery by using adb, button combo or rom manager.
Click to expand...
Click to collapse
Whoops, at least you got it going again :good: maybe you can take a shot at a different one click .jar
The one click jar that I used in download mode was SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar *which you need to be rooted so use Root Checker App to make sure you are rooted if not Super One Click v 2.3.3 Short Fuse :good:<---{there needs to be a huge thanks button here}
If that does it from there reinstall Rom Manager and enjoy cwm Recovery, and I flashed Devil 1.6.1.zip from cwmR :cyclops:
* A few more poost and i can post links, sorry
I'm looking to flash AOKP onto my Tab Plus, and I have no idea where to start
It's on Honeycomb right now, I have no clue how to use Odin, all I want is to flash AOKP in the easiest way possible.
I got my Tab yesterday, so it's just come from stock
johnnzey said:
I'm looking to flash AOKP onto my Tab Plus, and I have no idea where to start
It's on Honeycomb right now, I have no clue how to use Odin, all I want is to flash AOKP in the easiest way possible.
I got my Tab yesterday, so it's just come from stock
Click to expand...
Click to collapse
I highly recommend you let the tab do the OTA and check out the stock ICS first. THe Stock ROMs are more stable than any of the CM10 based ROMs and you will lose your IR remote functions on CM10 / AOKP/
but if you want CM10 / AOKP
First flash CWM
http://forum.xda-developers.com/showthread.php?t=2004835
Then follow steps in ROM you want to install.
Follow steps carefully because there is a hard brick bug in some of these tablets and if you wipe the system improperly you can permanently brick your device.
DigitalMD said:
I highly recommend you let the tab do the OTA and check out the stock ICS first. THe Stock ROMs are more stable than any of the CM10 based ROMs and you will lose your IR remote functions on CM10 / AOKP/
but if you want CM10 / AOKP
First flash CWM
http://forum.xda-developers.com/showthread.php?t=2004835
Then follow steps in ROM you want to install.
Follow steps carefully because there is a hard brick bug in some of these tablets and if you wipe the system improperly you can permanently brick your device.
Click to expand...
Click to collapse
Thanks for the reply. c:
How do I flash CWM using Odin?
bump, any help? ._.
follow this: http://forum.xda-developers.com/showthread.php?t=1777003
I prefer the Heimdall for CMV
johnnzey said:
bump, any help? ._.
Click to expand...
Click to collapse
BUMP???
Did you read my reply to you???
I has all the information to load CWM by odin.
What's the use of me typing this stuff if you don't read it?
DigitalMD said:
BUMP???
Did you read my reply to you???
I has all the information to load CWM by odin.
What's the use of me typing this stuff if you don't read it?
Click to expand...
Click to collapse
I, dont know HOW to use Odin!
johnnzey said:
I, dont know HOW to use Odin!
Click to expand...
Click to collapse
SOrry I thought there was a guide in the forum.
ok
- Download your stock ROM
- If its a zip, extract all and there should be a P62xxxxxxxxxxxxx_HOME.tar.md file
- Open Odin 1.85 or 1.87
- Restart the device into download mode (Press Home Button + Power Button + Volume down)
- Connect tablet to USB and wait until you get a yellow/blue sign in Odin
- Add P62xxxxxxxxxxxxx_HOME.tar.md5 to PDA (click PDA block and point to the file your extracted)
- Make sure re-partition is NOT ticked
- Click start ..... Start flash, sit back and wait a few minutes
- When finished, you should see a green message "SUCCESS" on ODIN
- Reboot your device and Voila!
Thus changing cwm to 6.0.1.9 will fix the hard brick issue? I aso upgraded my niece tab to stock ics but im worry it might hard brick her device later on.
Ps i check using emmc checker and her device is affected.
Sent from my GT-I9300 using xda app-developers app
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Zackpip said:
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Click to expand...
Click to collapse
Flash the latest @Android-Andi Philz Touch or TWRP recovery and that should solve the problem (I recommend flashing the recovery with Odin or Heimdall.) Status 7 error usually means outdated recovery.
Link to @Android-Andi's recovery thread: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Zackpip said:
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Click to expand...
Click to collapse
What exactly did you do that it did this? Did you attempt to flash the recovery in Odin or Heimdall? If Odin, which version?
Sent from my SGH-T989
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Zackpip said:
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Click to expand...
Click to collapse
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
jrc2 said:
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
Click to expand...
Click to collapse
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Zackpip said:
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Click to expand...
Click to collapse
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
jrc2 said:
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Zackpip said:
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Click to expand...
Click to collapse
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
jrc2 said:
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Zackpip said:
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Click to expand...
Click to collapse
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
jrc2 said:
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Zackpip said:
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Click to expand...
Click to collapse
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
jrc2 said:
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
Click to expand...
Click to collapse
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Zackpip said:
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Click to expand...
Click to collapse
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
jrc2 said:
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did exactly that.
Zackpip said:
Yes, I did exactly that.
Click to expand...
Click to collapse
So it must have been a bad download then. You used Odin v1.87 or what? Also, you should add [SOLVED] to the thread title.
Sent from my SGH-T989