[Q] Help! Gnex-vz Bricked and cant get to stock from odin - Samsung Galaxy Nexus

Tried changing my Dpi and now im at a black screen after the google logo. Volume up doesn't work so get get into bootloader. In oden mode but the drivers dont work to use oden3. Reinstalled them dozens of times.

sully112277 said:
Tried changing my Dpi and now im at a black screen after the google logo. Volume up doesn't work so get get into bootloader. In oden mode but the drivers dont work to use oden3. Reinstalled them dozens of times.
Click to expand...
Click to collapse
You have to use volume up and down at the same time. So press both volume buttons and power button at the same time to get into the bootloader.
Sent from my trasbeaned Galaxy Nexus.

thegtfusion said:
You have to use volume up and down at the same time. So press both volume buttons and power button at the same time to get into the bootloader.
Sent from my trasbeaned Galaxy Nexus.
Click to expand...
Click to collapse
I understand that but my volume up button does not work. stopped working randomly about two weeks ago. Therefore I can not get into bootloader. Only odin mode. So once in odin I cant get odin to see the gnex. I imagine its the drivers but they seem to be installing ok. Anybody have any ideas or am i screwed? I also took it apart to see if i could see something wrong with volume up button. No luck

Do you have USB Debugging enabled in your settings? If so, boot your device (yes, I understand that you will only see a black screen, but it doesn't matter) and plug into your PC. Once it is fully booted, open a command prompt on your PC and type: adb reboot bootloader
Then you can get into your recovery and then follow the instructions here.

efrant said:
Do you have USB Debugging enabled in your settings? If so, boot your device (yes, I understand that you will only see a black screen, but it doesn't matter) and plug into your PC. Once it is fully booted, open a command prompt on your PC and type: adb reboot bootloader
Then you can get into your recovery and then follow the instructions here.
Click to expand...
Click to collapse
It was enabled before the issue. Thanks for the advise but t gave up trying to fix it. Its my company line so I just ported my number to a temp phone and awaiting a replacement from assurion. Cant afford it being out of service too long. Guess i will just start over. But this time no hardware issues so bootloader wont be a problem again.

Related

[Q] Recovering from a soft-brick help [Volume Up and ADB not working]

Hello,
I am stuck in a unique situation for which I did not find any answer while searching this forum. Any help is appreciated.
I have CM 10 installed on my S3 and am currently stuck in an infinite boot loop (forever stuck on the Cyanogenmod splash screen at boot-up). The problem is, I can't enter recovery because my Volume UP key does not work. I also tried ADB, and it won't detect my phone because most probably it does not have USB debugging enabled.
I have the necessary drivers for S3 installed and know for a fact that ADB is working, because it can see my wife's S3 just fine and I can send commands to it. Yet, it cannot detect my S3.
ODIN *CAN* detect my phone, but since I cannot enter download mode....I can't flash anything.
Is there anything I can try to get into recovery? Or anything else? Thanks for the help.
Download mode is volume down+power+home, you should have no problem getting to download mode.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
Download mode is volume down+power+home, you should have no problem getting to download mode.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
After doing this, the phone first shows a warning screen and tells you to press Volume UP to continue, which, I can't.
sulhaq said:
After doing this, the phone first shows a warning screen and tells you to press Volume UP to continue, which, I can't.
Click to expand...
Click to collapse
This same thing happened to me today, and I am now stuck in ODIN mode, which sucks because I have a Mac and cannot get odin on my machine (to my knowledge)

[Q] I'm stuck in a bootloop

Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Clodio69 said:
Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Click to expand...
Click to collapse
Well, it looks like you have a couple of things going on. I can't remember how I got windoze to recognize the n7, but it had something to do with deleting the driver then plugging the n7 back in and letting it install the driver again. I remember I had to play around with the thing for a little while. Trying to update the driver wouldn't work for me either. As, far as the bootloop, you could try this one click tool: http://forum.xda-developers.com/showthread.php?t=2381582 Finally, you could try wugfresh's toolkit if you want to take the lazy route. It actually works pretty well. It might even help with that driver issue. http://forum.xda-developers.com/showthread.php?t=2389107 you don't use it to install a rom, but you do need to install a custom recovery and the toolkit could help with things like that. I personally use the toolkit to return a tablet or phone back to factory condition, lock the bootloader, etc...
You could also try to do a factory reset from the stock recovery. That fixed a boot loop for me after unlocking my bootloader.
Problem solved
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Thanks
Claude:laugh:
Clodio69 said:
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Click to expand...
Click to collapse
That's what I was referring to in my post, sorry for not giving a more detailed explanation.
Glad to hear you that you had a good experience with Google support and that you solved your problem. :good:
Thanks for giving feedback and have lots of fun with your N7!
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
frozst said:
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
Click to expand...
Click to collapse
Let me get this straight....are you trying to hold volume up & down at the same time? If so, you cannot please both volumes at the same time. Also, to boot into the bootloader (same as fastboot, not recovery) is power + volume down. The easiest way to do this is to hold volume down, then press and hold the power button. If the tab was on, and the screen goes black, let go of the power button, but keep holding the volume down button. It should boot into the bootloader soon enough.
1. Push volume up and power button for 5 seconds then release the power button.
2. Do a complete wipe of the system and reinstall the system.zip again and reboot.
If it doesnt load the recovery do this.:
1. Hold volume down and power button for 5 sec. Release the power button and volume once you enter the download screen.
2. Use odin in your Pc to install the rom you want or stock rom.
(3. If you installed stock rom go back to the steps I wrote at the top and flash a new rom)
Remember that you need to be rooted.
OK so I was trying with the wrong combination.
With both vol up/down + power worked.
I restored and it's up and running again.
Thanks!
Sent from my Nexus 4 using Tapatalk now Free

[Q] *Help Google nexus 7*

While attempting to flash PA Rom and Gapps, the device turned on and kept saying unfortanately, setup wizard has stopped.
a suggestion was to hold all three buttons at once for 15 seconds. Now the device is completely off screen and responds to no buttons. but when i plug it into PC it makes the sound of hardware connected. Please help
*update*
i fixed the black screen but now all i get is Unfortanately, Setup wizard has stopped
There is no way i can go to the settings to enable USB debugging.
there is no way i can access recovery without USB debugging
I can only access recovery with Nexus toolkit
which requires usb debugging
what do i do?
arbitercu said:
While attempting to flash PA Rom and Gapps, the device turned on and kept saying unfortanately, setup wizard has stopped.
a suggestion was to hold all three buttons at once for 15 seconds. Now the device is completely off screen and responds to no buttons. but when i plug it into PC it makes the sound of hardware connected. Please help
Click to expand...
Click to collapse
Make sure the device is turned off(press the power button for 10 seconds). Then press power & volume down until you get into the bootloader menu and from there get into recovery.
If you haven't made a backup in custom revoery then
Then connect Tablet to your PC and download+run this one click restore kit by ATGAdmin
NovaSense said:
Make sure the device is turned off(press the power button for 10 seconds). Then press power & volume down until you get into the bootloader menu and from there get into recovery.
If you haven't made a backup in custom revoery then
Then connect Tablet to your PC and download+run this one click restore kit by ATGAdmin
Click to expand...
Click to collapse
Sorry I dont understand much,
once im in recovery mode, it shows me a picture of an android with a caution sign coming out of its chest,
what do i do then?
sorry im a n00b
arbitercu said:
Sorry I dont understand much,
once im in recovery mode, it shows me a picture of an android with a caution sign coming out of its chest,
what do i do then?
sorry im a n00b
Click to expand...
Click to collapse
nevermind i got it to work, Thanks Man!
arbitercu said:
nevermind i got it to work, Thanks Man!
Click to expand...
Click to collapse
Glad it worked, sorry I was busy playing BF4 and didn't tell you need to use volume key to scroll to recovery and then press power button to boot into recovery.
But that recovery mode picture alone is enough if you are running the one click restore tool.

Did I ruin my phone?

Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app
Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.

Stuck at SAMSUNG LOGO

if you are stuck at samsung logo after flashing with odin
here's what you have to do:
1. While on Samsung logo. press power key + volume up and down + home button (all together)
2. When the screen is off. Press Power key + Volume Up + home button to enter recovery mode.
3. Wipe Data
4. Wipe Cache
5. Reboot to system
you should be fine right now ^^
cheers!
lexjay said:
if you are stuck at samsung logo after flashing with odin
here's what you have to do:
1. While on Samsung logo. press power key + volume up and down + home button (all together)
2. When the screen is off. Press Power key + Volume Up + home button to enter recovery mode.
3. Wipe Data
4. Wipe Cache
5. Reboot to system
you should be fine right now ^^
cheers!
Click to expand...
Click to collapse
I'm having that problem now. I followed your instructions and got to the recovery mode or "Odin Mode" and it's been saying it's downloading for about 10 min or so. Any idea on how long it should take ?
casual167 said:
I'm having that problem now. I followed your instructions and got to the recovery mode or "Odin Mode" and it's been saying it's downloading for about 10 min or so. Any idea on how long it should take ?
Click to expand...
Click to collapse
Actually I believe it's the download mode that I'm in. It doesn't seem to get to the recovery mode when I press the Volume up key and power button for some reason.. Am I doing something wrong
casual167 said:
Actually I believe it's the download mode that I'm in. It doesn't seem to get to the recovery mode when I press the Volume up key and power button for some reason.. Am I doing something wrong
Click to expand...
Click to collapse
Follow these instructions implicitly.
Hold POWER + VOL DOWN + HOME.
As soon as it restarts change to VOL UP while still holding the other buttons.
Do NOT let go of any of the buttons until recovery boots.
ashyx said:
Follow these instructions implicitly.
Hold POWER + VOL DOWN + HOME.
As soon as it restarts change to VOL UP while still holding the other buttons.
Do NOT let go of any of the buttons until recovery boots.
Click to expand...
Click to collapse
That's what I've been doing exactly but for some reason it just goes right back to the logo screen. I was able to get into the recovery mode one time out of 100 and I went through the process of factory reset but it didn't solve the problem. Now I can't get back into it. It's weird because I have no problem getting into the download mode pressing the volume down but volume up doesn't seem to work. Not sure why or what to do
I'd try reflashing stock recovery then try booting into it again.
If it flashes then you should be able to boot into it.
http://www.mediafire.com/?qyybs0m1yln443x
ashyx said:
I'd try reflashing stock recovery then try booting into it again.
If it flashes then you should be able to boot into it.
http://www.mediafire.com/?qyybs0m1yln443x
Click to expand...
Click to collapse
How exactly would I do that? I'm not to inclined when it comes to this stuff so any help you can give would be appreciated
Install Samsung usb drivers, put your tab into download mode, connect to pc, run Odin, load the file into the AP slot then click start.
http://forum.xda-developers.com/attachment.php?attachmentid=3109599&d=1420980613
i think i bricked mine...
These are the 2 screens i get whenever i try anything
joker616 said:
i think i bricked mine...
These are the 2 screens i get whenever i try anything
Click to expand...
Click to collapse
You haven't bricked anything, there could be any number of reasons why it won't boot past the logo.
Easiest way to resolve it would be to reinstall the stock rom.
The second image is download mode.
joker616 said:
i think i bricked mine...
These are the 2 screens i get whenever i try anything
Click to expand...
Click to collapse
That's the exact same situation I'm in. Every time I restart it I can't get passed that damn Samsung logo screen. I tried the whole flash with Odin process but I realized that when I connect the tablet to the computer, I get an "MTP Device Driver Failed" message so I'm assuming since the computer doesn't recognize it, even tried with KEIS and it doesn't, that I'm unable to complete the Odin job because that goes until 'Initialization' and stops there. Were you able to fix yours?
casual167 said:
That's the exact same situation I'm in. Every time I restart it I can't get passed that damn Samsung logo screen. I tried the whole flash with Odin process but I realized that when I connect the tablet to the computer, I get an "MTP Device Driver Failed" message so I'm assuming since the computer doesn't recognize it, even tried with KEIS and it doesn't, that I'm unable to complete the Odin job because that goes until 'Initialization' and stops there. Were you able to fix yours?
Click to expand...
Click to collapse
Are you saying you still can't get into recovery mode?
Also what is your device model?
ashyx said:
Are you saying you still can't get into recovery mode?
Also what is your device model?
Click to expand...
Click to collapse
No I can't. I've tried a thousand times in all different sequences of holding the three buttons and it just doesn't go. It's SM-T800. They screen shots on the first page is exactly what I get. Either the logo screen when trying to get into recovery or download mode which it has no problem going into.
casual167 said:
No I can't. I've tried a thousand times in all different sequences of holding the three buttons and it just doesn't go. It's SM-T800. They screen shots on the first page is exactly what I get. Either the logo screen when trying to get into recovery or download mode which it has no problem going into.
Click to expand...
Click to collapse
The two files below should boot you directly into recovery as soon as you start the tablet if you can flash them. Flash with Odin from the AP slot.
Make sure you put the device into DOWNLOAD mode first then connect your usb cable!
You can then do a factory reset and then try and flash the stock rom.
Stock recovery
Twrp recovery
.
ashyx said:
The two files below should boot you directly into recovery as soon as you start the tablet if you can flash them. Flash with Odin from the AP slot.
Make sure you put the device into DOWNLOAD mode first then connect your usb cable!
You can then do a factory reset and then try and flash the stock rom.
Stock recovery
Twrp recovery
.
Click to expand...
Click to collapse
Yeah I tried that too but when I connect the tablet to my comp, I get this 'Samsung Mobile MTP Device Failed' message so my comp doesn't even recognize the tablet. I even tried connecting with KEIS but that doesn't see it either because of that error. Idk if that's related to this issue that I'm having but I'm assuming that since the comp doesn't recognize the tablet because of that error, it won't finish the ODIN job. I get up to 'Initialization' and nothing after. I tried uninstalling and reinstalling the Samsung drivers and that didn't work either. Seems I can't catch a break here
casual167 said:
Yeah I tried that too but when I connect the tablet to my comp, I get this 'Samsung Mobile MTP Device Failed' message so my comp doesn't even recognize the tablet. I even tried connecting with KEIS but that doesn't see it either because of that error. Idk if that's related to this issue that I'm having but I'm assuming that since the comp doesn't recognize the tablet because of that error, it won't finish the ODIN job. I get up to 'Initialization' and nothing after. I tried uninstalling and reinstalling the Samsung drivers and that didn't work either. Seems I can't catch a break here
Click to expand...
Click to collapse
Mtp, kies and anything else is irrelevant, they are OS dependent.
Just put the tablet into download mode. Download mode works in boot loader mode. No need for the os.
ashyx said:
Mtp, kies and anything else is irrelevant, they are OS dependent.
Just put the tablet into download mode. Download mode works in boot loader mode. No need for the os.
Click to expand...
Click to collapse
Ok than Idk why it doesn't go passed the 'Initialization'. I tried multiple times and keep getting stuck on that
casual167 said:
Ok than Idk why it doesn't go passed the 'Initialization'. I tried multiple times and keep getting stuck on that
Click to expand...
Click to collapse
Ok we need to take this step by step as theres something amiss here.
DID YOU AT ANY POINT WHILE THE TABLET WAS WORKING ENABLE 'REACTIVATION LOCK'?
1. Ensure the Samsung drivers are installed (important) Samsung usb driver
2. Before connecting anything to the PC put the tablet in DOWNLOAD mode first.
3. Plug the USB cable into a USB 2 port
4. Wait for the 'ADDED' message (if you dont get this it wont work)
5. Load the tar file into the AP slot.
6. Click START
7. If it doesn't start to flash reboot the tablet directly back into DOWNLOAD mode without touching anything else then unplug and replug the USB cable back in.
8. If it still doesn't flash try ODIN 3.07 ODIN
9. Report back and post a screenshot (if it doesn't work).
ashyx said:
Ok we need to take this step by step as theres something amiss here.
DID YOU AT ANY POINT WHILE THE TABLET WAS WORKING ENABLE 'REACTIVATION LOCK'?
1. Ensure the Samsung drivers are installed (important) Samsung usb driver
2. Before connecting anything to the PC put the tablet in DOWNLOAD mode first.
3. Plug the USB cable into a USB 2 port
4. Wait for the 'ADDED' message (if you dont get this it wont work)
5. Load the tar file into the AP slot.
6. Click START
7. If it doesn't start to flash reboot the tablet directly back into DOWNLOAD mode without touching anything else then unplug and replug the USB cable back in.
8. If it still doesn't flash try ODIN 3.07 ODIN
9. Report back and post a screenshot (if it doesn't work).
Click to expand...
Click to collapse
I know for a fact that I never enabled the Reactivation Lock.. But you know, after literally days and hours including my entire weekend just searching the internet and trying every possible fix scenario that people have tried, I just gave in and sent it to Samsung this afternoon to have them fix it. Nothing I was doing seemed to work and I do believe I tried everything within my little knowledge to try. Let me ask you though, when I get it back in normal working order, would going through the steps to install the TWRP recovery and a ROM prevent me from being in this situation again or at least be able to actually fix it on my own?
If you dont mind tripping Knox and possibly warranty then I believe installing custom recovery is one of the best tools you can Install to a device.
It can get you back to a working state in minutes if you make a full backup.
It's a no brainer to install custom recovery if you intend to root and modify the device in any way.

Categories

Resources