I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
{
"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"
}
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
QUOTE=Drschplatt;69922876]I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.[/QUOTE]
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
---------- Post added at 06:22 PM ---------- Previous post was at 06:09 PM ----------
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
Click to expand...
Click to collapse
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
I appreciate the reply, but I am already able to get into download mode and can connect my tablet using Odin. I was even able to flash the stock rom as the photo in my post showed. So I'm a little confused. How is a jig going to help me? Isn't that just for accessing download mode?
What I cannot access is recovery.
Drschplatt said:
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
Click to expand...
Click to collapse
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Eddie Hicks said:
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Drschplatt said:
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Click to expand...
Click to collapse
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Eddie Hicks said:
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Click to expand...
Click to collapse
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Drschplatt said:
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Click to expand...
Click to collapse
I haven't been using ADB for awhile and I forgot the particulars. I just tried ADB rebooting to recovery from download mode and it doesn't work. Did you enable USB debugging in Developers options? If not in setting go to about device, tap on build number about 7 times and it will let you access Developers options, there you can enable USB debugging. You may also need to install drivers for your tablet if you already haven't. I forgot did you say your tablet reboots to download mode or you use your buttons? If you can get to any screen besides download you can try ADB reboot to recovery from there. There is a lot of things you can do like install recoveries if you can only get ADB and fastboot to recognize your tablet. There are other people who are way more knowledgeable with ADB than I am. Maybe you can search around for advice. Sorry if I got your hopes up and it doesn't work but I guess it never hurts to try.
Related
Problem Solved (Mostly).....
Android_Noob_2k12 said:
I was in recovery because I was going to flash a new rom and I accidentally hit reboot instead of back after wiping my old rom and now my note 2 won't start up. What the f**k do I do now. I really need to get back to stock rom and don't know what to do. HELP ME PLEASE.
Click to expand...
Click to collapse
Can you still get into recovery?
If so, just flash the stock rom.
Otherwise, if you mean that your note 2 won't start up at all, try getting into download mode.
If you can access download mode, use odin to get back to stock.
As long as you can get into download mode, there is no reason to panic
jc830 said:
Can you still get into recovery?
If so, just flash the stock rom.
Otherwise, if you mean that your note 2 won't start up at all, try getting into download mode.
If you can access download mode, use odin to get back to stock.
As long as you can get into download mode, there is no reason to panic
Click to expand...
Click to collapse
It won't start up at all and I don't think I can get Odin because I have a Mac.
jc830 said:
Can you still get into recovery?
If so, just flash the stock rom.
Otherwise, if you mean that your note 2 won't start up at all, try getting into download mode.
If you can access download mode, use odin to get back to stock.
As long as you can get into download mode, there is no reason to panic
Click to expand...
Click to collapse
How do I get to download mode?
Android_Noob_2k12 said:
How do I get to download mode?
Click to expand...
Click to collapse
Volume Down + Home + Power
If green screen pops up, press volume up to get into download mode
Let me know if you can get into download mode
Hold home power and volume down
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
And where do I get a stock rom if Icahn get into download mode because I got one from sammobile and it didn't work
jc830 said:
Volume Down + Home + Power
If green screen pops up, press volume up to get into download mode
Let me know if you can get into download mode
Click to expand...
Click to collapse
Even if I can get to download I can't get Odin because I don't have a pc
I can get to download mode
{
"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"
}
Android_Noob_2k12 said:
And where do I get a stock rom if Icahn get into download mode because I got one from sammobile and it didn't work
Click to expand...
Click to collapse
So it is possible to get into download mode?
I couldn't locate a stock rom that could be used with odin
As long as you can access the download mode you are fine now.
I would wait around a bit to allow some time for developers to come by this post to give you further assistance
As far as I know, you need a .tar file to use with odin.
Since I could not locate the tar file, I will have to let you get advice from someone else.
My apologies
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Android_Noob_2k12 said:
I can get to download modeView attachment 1612786
Click to expand...
Click to collapse
Sorry I can't help you further.
But be relieved that your phone 'will be' fine.
jc830 said:
So it is possible to get into download mode?
I couldn't locate a stock rom that could be used with odin
As long as you can access the download mode you are fine now.
I would wait around a bit to allow some time for developers to come by this post to give you further assistance
As far as I know, you need a .tar file to use with odin.
Since I could not locate the tar file, I will have to let you get advice from someone else.
My apologies
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Sorry I can't help you further.
But be relieved that your phone 'will be' fine.
Click to expand...
Click to collapse
Doesn't seem fine ATM. But I guess we'll see.
One advice that I will give you is to READ more.
I can't say that I know much, but the fact that you do not even know how to access download mode tells me that you need to learn heck of a lot more.
Being able to access download mode indicates that your phone isn't 'bricked.'
Download mode is what Samsung uses originally to install the roms through odin.
Hence, I can't guarantee your data, but your phone will be functional again - once your rescue arrives.
READ more. Reading more won't hurt a bit - especially when you are faced with the situation that you are in
Use heimdall. And i'm pretty sure sammobile has all available stock roms for the Note2
bluntman420 said:
Use heimdall. And i'm pretty sure sammobile has all available stock roms for the Note2
Click to expand...
Click to collapse
Ah, I just located it.
Android_Noob_2k12 - here's my solution.
As I am not familiar with mac, find a pc, download PDA from sammobile, use odin to push it while in download mode.
jc830 said:
Ah, I just located it.
Android_Noob_2k12 - here's my solution.
As I am not familiar with mac, find a pc, download PDA from sammobile, use odin to push it while in download mode.
Click to expand...
Click to collapse
I have absolutely no way of getting a pc. I do not live in or near the city and every computer at my house is a Mac.
bluntman420 said:
Use heimdall. And i'm pretty sure sammobile has all available stock roms for the Note2
Click to expand...
Click to collapse
I already tried to use the stock rom from the sammobile site it didn't work. But I will look into heimdall.
jc830 said:
One advice that I will give you is to READ more.
I can't say that I know much, but the fact that you do not even know how to access download mode tells me that you need to learn heck of a lot more.
Being able to access download mode indicates that your phone isn't 'bricked.'
Download mode is what Samsung uses originally to install the roms through odin.
Hence, I can't guarantee your data, but your phone will be functional again - once your rescue arrives.
READ more. Reading more won't hurt a bit - especially when you are faced with the situation that you are in
Click to expand...
Click to collapse
It's not that I didn't know how to get to download made, it's that I didn't know there was such thing as download mode. When I rooted my phone I did it all on my phone through equinox abuse apk and goo manager so I wouldn't have to deal with crap like download mode and Odin and all of that since I can't even use Odin with a Mac. And believe me when I say that I have been reading. I have not left my computer since this happened.
Okay I am going to use heimdall as it works for Mac. I will try to get the stock AT&T rom from sammobile again but I don't see why it will work this time considering it didn't work last time. What do I use to clean up any remaining root software after I get the stock rom flashed? And how to I return it to a un-modified state so I can return to att and get a new one that has a working SIM card reader.
Android_Noob_2k12 said:
Okay I am going to use heimdall as it works for Mac. I will try to get the stock AT&T rom from sammobile again but I don't see why it will work this time considering it didn't work last time. What do I use to clean up any remaining root software after I get the stock rom flashed? And how to I return it to a un-modified state so I can return to att and get a new one that has a working SIM card reader.
Click to expand...
Click to collapse
First I'll assume you're on att. You can get the stock unrooted att rom here: http://forum.xda-developers.com/showthread.php?t=2076745
Second, assuming heimdall works like odin does, youll flash the md5 file you downloaded from the above link and this will wipe your phone. No root, no customization, no data, nothing.
Sent from my SAMSUNG-SGH-I317
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Finally, once you have a stock phone again, if you have the modified count > 0 in the download screen, youll have to follow these directions to clear count: http://forum.xda-developers.com/showthread.php?t=1992303
Edit: last things. You'll have to be able to connect to your phone through your mac using the necessary usb drivers. You may be able to find a pc at a library or coffee shop, etc... this will teach you to be a mac fanboi good luck
Sent from my SAMSUNG-SGH-I317
Android_Noob_2k12 said:
I was in recovery because I was going to flash a new rom and I accidentally hit reboot instead of back after wiping my old rom and now my note 2 won't start up. What the f**k do I do now. I really need to get back to stock rom and don't know what to do. HELP ME PLEASE.
Click to expand...
Click to collapse
I did the same thing last week. Easy fix. Power off first, remove battery if you have to
1. boot into recovery (vol up+home+power)
2. select mounts and storage
3. select mount usb storage
4. copy your rom onto the sdcard in one of the folders
5. unmount usb
6. select install zip from sdcard
7. select choose zip from external sdcard
8. go to folder you copied rom and install
9. reboot
My friend from Korea bought a kfhd 8.9 here in the US and rooted it, but an OTA installed and bricked it. It keeps booting to the stock recovery. I tried getting fastboot to work, but the computer won't detect it, as well as the unbrick utility. Anything I can do?
It keeps booting to this
{
"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"
}
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
What attempts did you make to access fastboot?
Powering off, running cmd and typing fastboot -i 0x1949 getvar product, plugging it in. It doesn't detect my device.
I noticed that when I plug it in, Windows makes the beeping sound that tells you something is connected, and something briefly shows up in the hardware and devices section, but then disappears.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
You never know with Windows...Have you tried SoupKit?
rha_december said:
Nothing shows up in the device manager when plugged in as well. And I did install the drivers.
Click to expand...
Click to collapse
I would try to remove all the drivers you have now and install the non signed drivers from the first aid perferd drivers and that should go without any problems once that is done you should have a working drivers. Depending if you have windows 7 or 8 on how to disable driver signature.
Alrighty, thanks guys. I give it a shot.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
rha_december said:
I tried again on a different computer, and followed the instructions for KF First Aide package up until I had to plug it in. A driver installation window popped up and driver not found I can't go beyond that. I pressed 12 to install the Amazon ADB driver.
Click to expand...
Click to collapse
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
lizzord30 said:
I think the step your missing is to disable driver signature enforcement Search in google for disable driver signature enforcement Windows (then whatever version you have) and should find a way to do it, then connect kindle to the computer remove any drivers you see in device manager (and click delete driver if it gives you a check box) Then try the same thing and it should work! (cross all your fingers:fingers-crossed::fingers-crossed
Click to expand...
Click to collapse
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha. Thanks a lot for your help!
rha_december said:
I gave it a shot, but nothing is being picked up. Note that I can't even fully boot up the Kindle. It always goes straight to the stock recovery. Would an OTA disable ADB in the kindle?
UPDATE: Wow... I hit 9 to check fastboot status and it just happened to work, haha.
Click to expand...
Click to collapse
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
lizzord30 said:
:good::good: Great now that your in fastboot do you know what to do?
If you like could try my Rom but it will wipe your whole device(nothing on SDcard will be left)
here is the link if you like
It has some glitches still but it is automated from when your in fastboot. And dont forget to letup LMT on first boot.
Click to expand...
Click to collapse
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
rha_december said:
Hm, I actually tried to do a complete restore through fastboot, since it's the only thing working, but when it finishes and the kindle reboots, it still goes back to the stock recovery screen. I can't run the unbrick utility or use anything that requires ADB, since it's not being detected through that ><; damn it. I thought I was on to something.
Click to expand...
Click to collapse
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
lizzord30 said:
I was sending you that link because you don't need ADB to use what I linked, it goes right from fastboot.
Click to expand...
Click to collapse
Gotcha. Do you think I'll be able to boot up normally if I flash this?
rha_december said:
Gotcha. Do you think I'll be able to boot up normally if I flash this?
Click to expand...
Click to collapse
Maybe, hard to tell since like you said you tried to go back to completely stock and it didn't work.
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
rha_december said:
Alrighty, I flashed yours but I ended up with a red screen, but I figured out how to actually fix it. This kindle now run perfectly haha. awesome.
Click to expand...
Click to collapse
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
lizzord30 said:
Please post what you did so for the next person that has this problem can get it fixed!
Happy you got it working.
Click to expand...
Click to collapse
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
rha_december said:
I'll do that as soon as I have time to take screenshots and stuff. Just ran through the rain and jumped over a flooded road to get home >< soaking wet.
Click to expand...
Click to collapse
Ok thanks! I want to make a script to fix the red screen problem! I had it once but I forgot how I fixed it lol and I dont want to get it again to try to learn again how to fix
Pretty much all I did was get into fastboot via cmd, and flashed boot, system, and recovery individually; they were for 8.1.4. I was at work when I did it, so I can't remember where I got the files, but you get the idea.
However, I had to type: flashboot -i 0x1949 flash (whatever here) (dragged the file here)
Because putting the file in the same folder as my fastboot didn't work.
After that I just rebooted and it worked.
Hi All,
I've been trying to fix and upgrade error I got since two weeks ago. I found in this forum some related issue that I was trying but without luck.
I proceed to explain what I did to know if someone with more knowledge than me could kindly help, I really appreciate it.
[Device Information]
Samsung Galaxy Tab 3 7.0 (Wifi)
SM-T210
UK version
[Issue Description]
I was trying to root the device, I was searching for different approach to do it and the I select one to proceed, but it was so late and I was too tired that I forgot to enable debug mode, so I tried to update the tablet with a rooted firmware version. The process didn't work at all, but the tablet now is completely gone.
Actually, the tablet display the following information:
##########################################################################
ODIN MODE
PRODUCT NAME: SM-T210
CURRENT BINARY: Custom
SYSTEM STATUS: Official
HW REV: 0x5
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try 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"
}
[Steps done]
1. I download a couple of official firmwares but ODIN is always getting error trying to write into the Complete(Write) operation failed after NAND write operation at the beginning.
2. I've tried with ODIN v3.09 v3.07 v3.06 v3.04 v1.85 and v1.83.
3. If I try to connect to Kies, Kies try to connect to the device but enter in a loop trying to connect. I'm using Kies on WinXP, Win7 and MacOS. In all of them I got the same behavior (loop connection). I'm using the last Kies Version. Also I install serveral times the Samsung drivers. So, it's impossible to connect to Kies.
4. I'm searching for a official firmware and how to configure properly the ODIN but all the official firmware are stored on hotfile but now is not available anymore.
Could anyone of you help me to find a way to recover the tablet, it's the second week and I'm still in the same situation.
Thank you so much in advance.
Regards,
Nano.
nanodreams said:
Hi All,
I've been trying to fix and upgrade error I got since two weeks ago. I found in this forum some related issue that I was trying but without luck.
I proceed to explain what I did to know if someone with more knowledge than me could kindly help, I really appreciate it.
[Device Information]
Samsung Galaxy Tab 3 7.0 (Wifi)
SM-T210
UK version
[Issue Description]
I was trying to root the device, I was searching for different approach to do it and the I select one to proceed, but it was so late and I was too tired that I forgot to enable debug mode, so I tried to update the tablet with a rooted firmware version. The process didn't work at all, but the tablet now is completely gone.
Actually, the tablet display the following information:
##########################################################################
ODIN MODE
PRODUCT NAME: SM-T210
CURRENT BINARY: Custom
SYSTEM STATUS: Official
HW REV: 0x5
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
##########################################################################
[Steps done]
1. I download a couple of official firmwares but ODIN is always getting error trying to write into the Complete(Write) operation failed after NAND write operation at the beginning.
2. I've tried with ODIN v3.09 v3.07 v3.06 v3.04 v1.85 and v1.83.
3. If I try to connect to Kies, Kies try to connect to the device but enter in a loop trying to connect. I'm using Kies on WinXP, Win7 and MacOS. In all of them I got the same behavior (loop connection). I'm using the last Kies Version. Also I install serveral times the Samsung drivers. So, it's impossible to connect to Kies.
4. I'm searching for a official firmware and how to configure properly the ODIN but all the official firmware are stored on hotfile but now is not available anymore.
Could anyone of you help me to find a way to recover the tablet, it's the second week and I'm still in the same situation.
Thank you so much in advance.
Regards,
Nano.
Click to expand...
Click to collapse
Can you boot into download mode? Hold Power, Volume Down, and Home button for 10-15 seconds until you see a warning about Download mode; then hit Volume Up to enter Download mode.
Recovery
Hi gr8nole!!
Thank you so much for your very fast reply.
[Steps done]
a. I've been checking different method to boot in different modes but it's not possible. If I try to boot in a download mode it loads the same screen.
b. I can only switch off the tablet (10-15 seconds power button), but there is not any other screen I can load. I've tried
1. Hold Power, Volume Down, and Home
2. Hold Power, Volume Up, and Home
3. Hold Power, Volume Down
4. Hold Power, Home
5. Hold Power, Volume Up
Apologize for not said that in my first post.
nanodreams said:
Hi gr8nole!!
Thank you so much for your very fast reply.
[Steps done]
a. I've been checking different method to boot in different modes but it's not possible. If I try to boot in a download mode it loads the same screen.
b. I can only switch off the tablet (10-15 seconds power button), but there is not any other screen I can load. I've tried
1. Hold Power, Volume Down, and Home
2. Hold Power, Volume Up, and Home
3. Hold Power, Volume Down
4. Hold Power, Home
5. Hold Power, Volume Up
Apologize for not said that in my first post.
Click to expand...
Click to collapse
Does Odin recognize when the tablet is connected via usb?
Sent from my DROID RAZR MAXX HD
You could try a jig.
Hi
Hi Guys!!
Odin Tool recognize the device, the tool show that the device is connected to the port COM3.
I didn't know about jig, I'll wait to know if it works with odin and if there is no any progress I'll buy the jig usb.
Thanks so much.
Regards,
Nano.
You should still get a jig anyhow, as they are only about £3.
Hello nanodreams, I had the same problem, did u solved it with Odin? or with the jig usb?
Let me know if you found the solution!!!
PLZ
same problem plz help me
nanodreams said:
Hi Guys!!
Odin Tool recognize the device, the tool show that the device is connected to the port COM3.
I didn't know about jig, I'll wait to know if it works with odin and if there is no any progress I'll buy the jig usb.
Thanks so much.
Regards,
Nano.
Click to expand...
Click to collapse
hey i have same problem as urs ...same things happend to me...if u solved it plz tell me how...i been dieing researching about this
can u plz let me know if any update plz:crying:
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
dnafredy said:
Hello nanodreams, I had the same problem, did u solved it with Odin? or with the jig usb?
Let me know if you found the solution!!!
PLZ
Click to expand...
Click to collapse
plz update if u solved it mate....i am stuck as same place u were stuck...plz help
67115 said:
hey i have same problem as urs ...same things happend to me...if u solved it plz tell me how...i been dieing researching about this
can u plz let me know if any update plz:crying:
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
plz update if u solved it mate....i am stuck as same place u were stuck...plz help
Click to expand...
Click to collapse
I have the same problem, please update if you have found the solution.
1st remove your external SD card....then do this
Boot to DL mode
Flash a CWM Recovery using Odin
Boot to Recovery
Format Every Single folder....an error will be found eg. Not found NVM just ignore it
Wipe Data..Cache and Delvik
Turn off device and go to DL mode
Flash back stock firmware using Odin. The above idea will wipe out every junk in the partitions for a fresh firmware to be pre-loaded.
Sent from my SM-T211 using XDA Premium 4 mobile app
Thanks but I cannot get into DL mode any key combination would get back into the Firmware issue screen and even when Odin mode is supposedly on according to the screen, Odin would not get pass the Setup Connection stage.
Sent from my XT1058 using XDA Free mobile app
From here forget about DL mode...with Odin follow the steps above..it should flash the CWM
Sent from my SM-T211 using XDA Premium 4 mobile app
Is there anyway to install a Recovery without a computer? Straight from the phone. .
Sent from my SM-G900P using XDA Premium 4 mobile app
I made it work according to a previous comment, Macbook was the culprit. I was able to flash CWM from another laptop.
Sent from my XT1058 using XDA Free mobile app
PMGRANDS said:
Is there anyway to install a Recovery without a computer? Straight from the phone. .
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if you know which block or patition your recovery lives in and you are rooted
you can use dd command. place recovery.img in /sdcard,
in terminal
cd /sdcard
then
dd if=recovery.img of=/dev/block/mmcblk0p#
# is the mmcblk where your recovery.img needs to be flashed. don't screw it up ! research!
meant in the best way :good:
m
ok i see lots of threads about G2 stuck at LG logo with no download mode etc but none specific to my situation so figured id start my own.
my phone is stuck at the lg logo when i try to boot, when i try to go to download mode it shows the blue dots but windows, flash tool, nothing will recognize the phone as being plugged in, and not even the little sound windows makes when a usb device is plugged in, its been a little while so i cant remember EXACTLY what the last thing i did that bricked it was, something i did on command line with aboot something, i can try to dig it up if absolutely necessary but it would take some digging...when i try to boot into recovery it freezes at the "loading recovery screen, when i try to go to download mode it sticks at the blue dots and wont respond to anything, when i try to do a factory hard data reset it says "hard reset processing" or something similar then freezes there, ive tried reinstalling the drivers, using different pcs, read through countless threads, but have had no luck, any ideas what i can do to unbrick my brand new g2?? thanks in advance
Change PC and try
Sent from my XT1022 using Tapatalk
xbabyboy4021x said:
ok i see lots of threads about G2 stuck at LG logo with no download mode etc but none specific to my situation so figured id start my own.
my phone is stuck at the lg logo when i try to boot, when i try to go to download mode it shows the blue dots but windows, flash tool, nothing will recognize the phone as being plugged in, and not even the little sound windows makes when a usb device is plugged in, its been a little while so i cant remember EXACTLY what the last thing i did that bricked it was, something i did on command line with aboot something, i can try to dig it up if absolutely necessary but it would take some digging...when i try to boot into recovery it freezes at the "loading recovery screen, when i try to go to download mode it sticks at the blue dots and wont respond to anything, when i try to do a factory hard data reset it says "hard reset processing" or something similar then freezes there, ive tried reinstalling the drivers, using different pcs, read through countless threads, but have had no luck, any ideas what i can do to unbrick my brand new g2?? thanks in advance
Click to expand...
Click to collapse
This is what i would do....looks like your cable works, looks like you know how to get into Download and Recovery Mode. You have to get it to be detected, if it boots into Download mode it should work. Try re-installing the drivers.
Here is the ZVC tot file if u dont have it: http://forum.xda-developers.com/showthread.php?t=2702422
Try this Tutorial: http://forum.xda-developers.com/showthread.php?t=2475045
pvinodnayak said:
Change PC and try
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
tried 3 different computers and windows 7 and 8....
youngnex said:
This is what i would do....looks like your cable works, looks like you know how to get into Download and Recovery Mode. You have to get it to be detected, if it boots into Download mode it should work. Try re-installing the drivers.
Here is the ZVC tot file if u dont have it: http://forum.xda-developers.com/showthread.php?t=2702422
Try this Tutorial: http://forum.xda-developers.com/showthread.php?t=2475045
Click to expand...
Click to collapse
that tutorial still leaves me stuck at trying to get the computer to recognize it and so far no luck! thanks for the info ill do that if i do gett it to recognize it...any other ideas?? im stuck!
xbabyboy4021x said:
tried 3 different computers and windows 7 and 8....
that tutorial still leaves me stuck at trying to get the computer to recognize it and so far no luck! thanks for the info ill do that if i do gett it to recognize it...any other ideas?? im stuck!
Click to expand...
Click to collapse
Your download mode is broken. The laf partition needs fixed.
I'm looking for a way to do it from recovery.
Sent from my Nexus 7 using Tapatalk
unless you can get into fastboot mode, your sol. I had this exact same thing happen to me, ended up having to get a replacement phone.
i fixed it! ...by taking it to sprint and getting a manufacturer warranty replacement lol...got tired of effin with it
Well that sucks. I have the same problem and I just need to get back into download mode. Is there a key combo for DL mode?
Sent from my SM-T217S
Bigt2003 said:
Well that sucks. I have the same problem and I just need to get back into download mode. Is there a key combo for DL mode?
Sent from my SM-T217S
Click to expand...
Click to collapse
with the phone off (completely), hold volume button (up i believe), and plug usb into computer. This should bring up download mode. If volume up doesnt work, try volume down. If you get just to the dots, then your download mode is broken.
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you
Long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I installed TWRP and erased all my device information without making a backup. During intallation something happened with the toolkit(I believe the program froze or I just got too impatient, so I disconnected the USB). Mind you at this point I had not installed any third party roms yet resides TWRP which I don't even know if it installed completely because after I disconnected the screen turned into bright static.
So after mindlessly disconnecting my phone the entire screen went blank or was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without an operating system because I wiped it when I had TWRP and I now see this after it loads https://goo.gl/photos/pNZz2XgpQ2oA3SMN6 I don't know what else they did over there because I no longer have TWRP. I also have a locked bootloader now. I attached some screen shots of what options I get when I turn on the phone and the other options I see. which include the bootloader and recovery screen.
https://goo.gl/photos/w7QnfuqtbNGirQuE9
https://goo.gl/photos/58XmdAiMwmdvGfr29
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. I also tried fastboot oem unlock, but it says failed. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am seeing; Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB (I am now able to do this thanks to some help in the forum)
EDIT: I fixed the driver issues, This involved manually assigning drivers TWICE through device manager. I had to assign them when I was in the bootloader and again when I went into recovery on my android device. Windows 8.1 recognized the device as 2 different devices based on what screen (bootloader vs recovery). Thus make sure to manually update your drivers twice. Once in bootloader and again in recovery. I am also using the latest android SDK platform tools.
I am now having trouble doing "adb sideload file.zip"... My device keeps rejecting googles OTA files saying signature verification failed https://goo.gl/photos/9UURn9To33YdZM7B7
I also get this error in CMD https://goo.gl/photos/dRvUS3bB5saGehX1A
EDIT: added more details
Last edit: Solved!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So none of the OTA roms from google worked in ADB sideload etc, but for whatever reason when I sideloaded a custom ROM it installed just fine... No sig verifications errors in recovery mode... I used http://forum.xda-developers.com/nexus-5x/development/rom-pure-nexus-layers-fi-wifi-calling-t3244601 <---- After downloading this custom rom file, I moved it over to my SDK platform tools folder (you could also use the adb folder in your C drive if you went about installing those adb drivers)
Next, I started bootloader on my android device by pressing power and volume down buttons. I then navigated to recovery by using the volume keys. once in recovery, I selected apply update from ADB. I am now done with the phone.
I opened up command prompt from my PC using shift/right click from the appropriate folder (c/adb or platform tools folder). further, I opened command prompt and typed in "adb sideload pure_nexus_bullhead-6.0-20151109.zip" the flash was successful.
The first boot was not perfect. I recieved a error in regards to something about a manufacture error, but it was enough for me to get into the OS and enable OEM unlocking. I am now able to move forward and unlock the bootloader with rootkit or fastboot. After unlocking the boot loader I went back to a factory ROM which now installed with no problem.
Holly crap. Anyways huge thanks to everyone on this thread you guys are awesome I could not have done it without you.
XDA 4 life
Can you be a little more specific? what were you flashing and what steps did you follow?
Bootloader
metpage said:
Can you be a little more specific? what were you flashing and what steps did you follow?
Click to expand...
Click to collapse
ideaman924 said:
Please include:
Details of what you were doing
A screenshot (or a camera shot from another phone)
What things you flashed
What the phone was running prior to flashing
Your device model (just in case we need to recommend tot files)
If possible, a recent backup from TWRP
We cannot help without these things. Thanks!
Click to expand...
Click to collapse
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
{
"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"
}
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
more pics
Nebula666 said:
Ok so here is the long story. I downloaded the Nexus rootkit and unlocked my bootloader in an attempt to root my device. I got half way through installing TWRP and erasing all my device information when my computer froze or something happened with the toolkit(I believe the program froze, so I disconnected). Mind you at this point I had not installed any third party roms or etc besides TWRP.
So after disconnecting my phone the entire screen went blank and was static. I could not see anything, so I sent it to LG for repair. They fixed the screen, but the phone is still without a operating system. I don't know what else they did over there because I no longer have TWRP. I have a locked bootloader now and no OS. I attached some screen shots of what options I get when I turn on the phone and the other options I see.
I have tried using the rootkit to install stock rom, but that requires an unlocked bootloader which I don't have. Also, I have tried installing the right drivers... It's hard to tell whether or not I have the correct drivers. Under device manager. I am Android Device--- LG Android Interface. I don't think these drivers work though because I can't pull up my device details in ADB, but that could also be because everything is wiped on the device...
I also have the latest SDK installed from google.
For the most part I am a noob, I know, but I ain't going down without a fight.
Click to expand...
Click to collapse
I do get these options by holding down the power key and volume down
Nebula666 said:
I do get these options by holding down the power key and volume down
Click to expand...
Click to collapse
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're booting into the bootloader which is a good start. Using the vol keys can you go to recovery? Is it the stock recovery. Also,I think your drivers are correct. When booted into the boot loader you need to use fastboot commands, not adb, i.e. fastboot devices
Edit, I see from your second image it's the stock recovery. Try loading the ota from here, https://developers.google.com/android/nexus/ota#bullhead
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried using fastboot devices and nothing comes up.. I am going to try reinstalling all the SDK/drivers on a different computer. Maybe that will help.
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Ok I think I am connected now...
Device manager is showing my device as
Android Devices
---Android Bootloader Interface
It is also now recognized in CMD.. before it would not show up.
jd1639 said:
Are you booted into the bootloader when you run fastboot devices? Power and vol down keys then stay on the screen with Start on it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok I am not sure what to do now as the google directions advise me to use ADB reboot recovery and that doesnt work...
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Ok so I tried running in recovery mode... I selected apply update from from ADB.... Than I ran the following command adb sideload (ota file.zip) from CMD and I got this error
"ERROR: DEVICE '(NULL)' NOT FOUND"
jd1639 said:
Just boot into the bootloader then use the vol keys to go to recovery
It's the same screen as the second image you posted.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
See above, I get this message "ERROR: DEVICE '(NULL)' NOT FOUND"
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
jd1639 said:
You get that error on your pc? I'm not sure what to tell you.
You got the device back from being repaired in this condition?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I get that error message from cmd after imputing adb sideload "ota file"
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Nebula666 said:
I get that error message from cmd after imputing adb sideload "ota file"
Click to expand...
Click to collapse
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
---------- Post added at 06:01 PM ---------- Previous post was at 05:43 PM ----------
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The OTA updates Google is supplying us are not simply delta updates. They are the full package. Google is doing it this way because the developer preview OTA was borking locked devices. The OP indicated that he is still locked. Oddly since he was flashing TWRP when this ****uation started. But that's the info we were given.
Sent from my SM-G930V using Tapatalk
Half way solved
metpage said:
You can't side load the ota if you don't have an OS installed. Download the the stock image from Android site and flash those images to get your device working. You need to be on the bootloader to flash them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
PiousInquisitor said:
While your phone is in the stock recovery and plugged into your computer type:
adb devices
What is the output?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Ok here is what is going on.... It was definitely a driver issue. I had the drivers successfully installed when I was in bootloader, but as soon as I went to recovery mode on android my computer would no longer recognize the drivers, so I had to manually reinstall them again for recovery mode. Now I have access... I did another attempt at adb sideload "ota.zip" that I downloaded from googles OTA site , but I am getting a signature error on my android and abort message on android here
Am i suppose to unzip this file or leave it zip? When I unzip all I see is a bunch of .img files not zny zips so maybe I am missing something here.
So google has two download links for the OTA, I am trying the other one now without unzipping it.
Alright so the second file I downloaded is giving me the same verification errors in recovery... I am going to try one last thing before I try blending the phone.
There is hope ahead! i think I downloaded the wrong OTA from the google website. The nexus 5x and 6p have the same descriptions. Hopefully this solves the problem. I am literally ready to throw this phone in the blender and call it a day