Related
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Edit: I was told that my lack of drivers were the problem - I thought I didn't need them on a 32 bit system. I did. Recovery reboot solved for me!
If you cannot enter Recovery Mode with Vol Up+Vol Down+Power, your phone is defective and T-Mo will exchange it.
You're serious? It really is that simple?
So, I call them up, tell them I have a hardware locked phone and I cannot boot into recovery mode, and they'll set me up?
I'm thinking I had to go learn odin and start getting less a'scared of command lines.
FenixGryph said:
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Click to expand...
Click to collapse
Here's my advice in a step-by-step:
-Install the AndroidSDK (And make sure it is named that) Found here - http://developer.android.com/sdk/index.html
-Move the folder to Computer> Local Disk ( C: )
-Run the .exe
-Go to Settings, click on Miscellaneous, and check Force https
-Click on Available Packages and install (And then minimize)
-Click Start and search cmd (Also known as Command Prompt)
-Type cd\ (And then press enter)
-Type AndroidSDK\Tools\adb reboot download (And then press enter)
**Make sure your phone is plugged into the computer with USB Debugging turned on.
Your phone will reboot and be in Download Mode. Hope this helps.
Hardware Locked, huh? really? on the vibrant?
Can someone explain what hardware locked vibrant is. Is this some term you guys made up. I can not for the life of me, figure out, why in the world Samsung would ship some phones hardware locked and others not.
Makes no sense, someone explain, seems like this is a made up term which does not apply to Vibrant.
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
sabooher said:
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
Click to expand...
Click to collapse
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Oniyuri said:
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
Well just my 2 cents on the topic, entering recovery mode required following strict steps, miss 1 single step, and you won't get into recovery.
now as far as download mode goes, I have been able to get into it once. This was by accident, I was randomly doing various sequences of volume rocker and power, it went into download mode. Now since then, I have no clue what sequence I used, but I have never been able to get into download mode ever again.
Additionally, my phone is dated 7/2010, so the 8/2010 batch theory doesn't hold since I can not get into download mode either now.
To get into Recovery Mode, follow these steps.
Okay, I'm reading lots of people having trouble getting into recovery mode, thinking their phone is broken or busted. Chances are you are not holding down the power button log enough, or you are letting go of something too quick.
FOLLOW THESE DIRECTIONS STEP BY STEP.
1) START with your phone off
2) Press volume up AND volume down at same time, keep them pressed in the entire time, do NOT let go. I prefer to hold my phone in landscape, this gives me better control with my fingers.
3) WHILE holding down volume up and volume down, press and hold power button, DO NOT LET GO OF ANYTHING. You should be holding down volume up, volume down, and power, DON'T LET GO! HOLD ON... and proceed to next steps, dont let go!
4) PHONE will start, you will see the white Vibrant logo. STILL DON'T LET GO, volume down, volume up, and power all pressed.
5) White Vibrant logo disappears, still dont let go!
6) White Vibrant logo re-appears again for the second time. Right when you see the white vibrant logo pop up a second time, let go of ONLY the power button, keep holding down volume down and volume up.
7) Phone enters recovery mode, you can let go the volume rocker.
hope this helps, it worked for me, hopefully it works for you also.
now can someone post sure fire method into getting into download without needing to connect the phone to your computer and using odin?
Oniyuri said:
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Click to expand...
Click to collapse
Hate to break it to you, my phone is made in July, and it WILL NOT go into download mode, I do however get into recovery mode.
That phone date batch theory doesn't hold true, so you can stop searching for july phones.
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.[/QUOTE]
where did you read this, please provide the link
Click to expand...
Click to collapse
Samsung Mobile USA support is worthless. I called three times and finally got someone in "premier support" who didn't know anything. He actually went as far as to tell me a simple data wipe would resolve this problem, ha! I then got a hold of someone at Samsung Telecom corporate office who said he'd look into it and never called me back. No surprise there either. I think it's kind of sad that people are having to resort to Facebook wall comments to get a company to start backing it's products.
Thanks to sabooher, I was able to get into download mode with no problems, I hope this works for you, and thank you again sabooher.
okay, start off with your phone turned off
hold down both volume down and volume up at the same time, do not touch the power button
now, get your usb cable, have one end into your computer, the other end put into your vibrant, while you are still holding down the volume up and volume down at same time. dont touch power button
your phone hopefully will now go into download mode!
SamsungVibrant said:
FOLLOW THESE DIRECTIONS STEP BY STEP.
Click to expand...
Click to collapse
Nope, no good.
jonathan3579 said:
Here's my advice in a step-by-step:
Click to expand...
Click to collapse
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
SamsungVibrant said:
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
where did you read this, please provide the link
Click to expand...
Click to collapse
Sure, it's all over their facebook page. I've read tons of android sites so I can't quote the site that led me to this page but I've been following the Samsung Mobile Canada FB page over the last few days about it. Suffice it to say: the Bell customers are really not pleased with the 3 btn issue: Samsung Mobile Canada
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
maybe you don't have the correct drivers installed, try the ones from this thread --> http://forum.xda-developers.com/showthread.php?t=728929
Well here's my take on things. I got my phone (July 11th build date) directly from T-Mobile corporate. Came via FEDEX on launch day. Long story, suffice to say I had Behold II and complained to the right people at the right time and got swapped a Vibrant to basically shut me up.
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
masterotaku said:
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
Click to expand...
Click to collapse
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
crazycaveman said:
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
Click to expand...
Click to collapse
I tend to have bad luck with Odin too. I've seen the "ohsh*t" icon many times...
(note: the "ohsh*t" icon is what I call the phone/caution symbol/pc icon I tend to see quite often)
When that happens the ONLY way I can get back to download mode is the battery-insert method.
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
It definitely sounds like you don't have the correct drivers installed. My drivers were downloaded through the installation of Kies, however, is your computer online while you are attempting this? I can only speak for my computer which is running Windows 7, but it automatically downloads any updated/new drivers necessary when connected online.
woot!
Ha ha!! The drivers were the problem. I was under the impression I only had to install the samsung drivers if I was on a 64 bit system.
I'm looking at my recovery menu now and am very happy! Wish I had time to do the stuff I wanted to do the vibrant before work, but I gotta make a couple of bucks before I get this guy set up just how I want.
See? I knew XDA was the place to be. Many thanks Oniyuri and jonathan3579!
first of all, props to JCase and Team AndIRC. you guys are awesome.
i am, however, experiencing some weirdness. whenever i choose "turn off" from the power menu my phone doesn't power down completely, it instead reboots to clockwork mod. isn't that bizzare? it happens every time with 100% repeatability. to completely power off the phone i have to pull the battery. is anyone else experiencing this behavior? that's so weird, right? i mean it's not really a big deal, but surely this is not the desired result.
at the home screen i hold the power button, choose "power off" and then 15 sec later i'm in clockwork recovery. bizzare.
can anyone help me? thanks to all in advance. c
P.S. as a side note, clockworkmod recovery 3.0.2.1 isn't very TB friendly. i think whomever wrote it forgot the TB has no trackball because by default the power button acts as the "back" button when it should really be the "enter" button. to get an "enter" button you have to wrap-around scroll a couple of times until you get the "Back menu button enabled" message. clockwork's only mode of operation on the TB should really be that the power button acts as "enter" and the back menu button is enabled.
EDIT 1: FIX BELOW
so i posted this question in the development section because it had to do with root and i thought that's where all the root discussion would be. mods moved it here. totally fine. keep it tidy. but then yesterday someone answered the question in a new thread in the development section. go figure. anyway, here's the solution as posted by "dbu":
dbu said:
This is all done in ROM Manager: clear your download cache, check erase recovery before flashing in the settings, re-flash latest CWM, be happy
Hit menu and you will see the button to clear the download cache, hit menu and then settings and you will see the check box to erase recovery.
Thank Slayher guys, not me, he's the one who fixed it
Click to expand...
Click to collapse
props to dbu and slayher
EDIT 2: MAYBE NOT FIXED
Some are saying that this does not solve their problem. My phone appears to power down when plugged in without going into recovery, but every now and then I do see it go into recovery when plugged in. Others see it every time, so there is still some residual weirdness. Your mileage may vary, as some would say. Who is using FastBoot in the Power settings? Maybe that is causing the phone not to power down as we would expect, but I am not a dev and I am just speculating.
Same issue here... Power down and plug in to charge. Few seconds later boots to recovery.
Same thing here...
Even in recovery if you select "power off" it reboots back into recovery.
upgrade to 3.0.2.2, that lets you hit "back" to "select" your choice.
For some reason powering down this phone while it is plugged in, sends it into Recovery. No one knows why yet. Actually I should say I don't know why, i'm sure a dev knows or could find out why.
Yup just noticed it this morning too, very strange.
Same for me.
same here....power down + usb charge = back to recovery
Please ask your questions in the appropriate forum.
This bug is known to be caused by having your phone plugged it to your cable. Unplug the phone first.
Thanks,
jcase
It still goes to CWM even after turning the phone off while unplugged and then plugging it in.
jcase said:
Please ask your questions in the appropriate forum.
This bug is known to be caused by having your phone plugged it to your cable. Unplug the phone first.
Thanks,
jcase
Click to expand...
Click to collapse
We need the Q&A Sub-Forum... asap lol
Any info on a fix for this??
jcase said:
Please ask your questions in the appropriate forum.
This bug is known to be caused by having your phone plugged it to your cable. Unplug the phone first.
Thanks,
jcase
Click to expand...
Click to collapse
The bug still exists, at least on my phone, even when I have it unplugged from the charger cable frist, power down, pull the battery, then put the battery back in and plug in the power cable. Within 30 seconds or so the phone boots back into Clockwork Recovery. Are others not experiencing that? It makes bump charging the battery impossible.
I'm curious, where should the OP have asked this? Each device seems to have a different set of protocols for what sub-section to ask/post in. I've been mostly in the Nexus S forums the last few months, and over there, this should have gone in the Q&A section, which we don't have here. Should it have been asked in the Dev section? In the root thread? Just curious...not being sarcastic or challenging!
g00s3y said:
We need the Q&A Sub-Forum... asap lol
Click to expand...
Click to collapse
I prefer the two sections merged personally; it's frustrating that the sub-forum structure isn't the same across all the devices.
distortedloop said:
Are others not experiencing that? It makes bump charging the battery impossible.
Click to expand...
Click to collapse
yeah, I posted the same thing on the previous page. Powering off while unplugged doesn't fix it. And the thread was originally in the development forum which seemed like the appropriate place since it's more of a cwm issue for developers to look into than general.
PJnc284 said:
yeah, I posted the same thing on the previous page. Powering off while unplugged doesn't fix it. And the thread was originally in the development forum which seemed like the appropriate place since it's more of a cwm issue for developers to look into than general.
Click to expand...
Click to collapse
I'm guessing everyone is having this problem... Or at least I hope (so there will be a fix quicker)
It was explained to me last night in the irc channel by scotty and jcase that it is supposed to do this, it has something to do with it being an emmc-boot phone with a custom recovery, there was a long explanation of a whole bunch of stuff I didn't really understand. I will say though, that the phone will charge in recovery, I turned it off last night, it went into recovery, and I woke up to a fully charged battery...
dbu said:
It was explained to me last night in the irc channel by scotty and jcase that it is supposed to do this, it has something to do with it being an emmc-boot phone with a custom recovery, there was a long explanation of a whole bunch of stuff I didn't really understand. I will say though, that the phone will charge in recovery, I turned it off last night, it went into recovery, and I woke up to a fully charged battery...
Click to expand...
Click to collapse
I may be wrong, but i'm one of those that believe the phone charges better completely turned off. I've just gotten used to this over the years. Maybe I will change my thought process. thanks for the explanation!!
dbu said:
It was explained to me last night in the irc channel by scotty and jcase that it is supposed to do this, it has something to do with it being an emmc-boot phone with a custom recovery, there was a long explanation of a whole bunch of stuff I didn't really understand. I will say though, that the phone will charge in recovery, I turned it off last night, it went into recovery, and I woke up to a fully charged battery...
Click to expand...
Click to collapse
I wonder if they keep a log of that chat room, I'd be interested in reading the explanation. Didn't jcase call it a bug on the previous page? Bug implies it can be fixed; design with emmc-boot implies not necessarily, but we're a bit above my paygrade in that discussion.
gwallers said:
I may be wrong, but i'm one of those that believe the phone charges better completely turned off. I've just gotten used to this over the years. Maybe I will change my thought process. thanks for the explanation!!
Click to expand...
Click to collapse
I've had over a dozen smartphones/pda type devices over the past 6 or so years...never turned them off to charge as a matter of routine; just when the battery died completely on me. I don't think it's necessary with the newer/smarter batteries they use. I've certainly noticed no significant difference in battery life whether it was charged while on or off on any of my phones. I'm still up in the air about whether bump charging works or not, there's enough anecdotal evidence that it does, along with a supposed letter from HTC suggesting the method, to give it some credibility, but my experience on the EVO was iffy.
PJnc284 said:
yeah, I posted the same thing on the previous page. Powering off while unplugged doesn't fix it. And the thread was originally in the development forum which seemed like the appropriate place since it's more of a cwm issue for developers to look into than general.
Click to expand...
Click to collapse
Must have missed your post, sorry for repeating it. I didn't notice this thread was moved; I agree this is probably the best section for it. Thanks.
This is /bump worthy simply because it needs to get addressed ASAP.
Although it seems to take a charge while sitting in recovery(with the led off), it's still annoying that it boots up at all.
I would also like to hear the explanation of this... as it's clearly a bug and should not happen.
I was on when he explained and he said that it does have to do with the phone having emmc storage. Normally on emmc phones when you plug it in to charge turned off, it boots into recovery but recovery knows to turn the screen off.
Sent from my SCH-I800 using Tapatalk
I've searched and searched, but I've been unable to find a solution to, or even any examples of, my particular problem. I was wiping and formatting everything before I flashing a ROM as I've done countless times before, but this time I decided to format the boot partition, which I can't remember ever doing before, and I think I then pulled the battery before flashing anything.
Now when I put the battery back in or plug in the USB cable (without pressing any buttons at all) the phone immediately shows the Vibrant/Samsung screen and nothing else happens. Holding the power button (or power + vol up, or power + vol down, or power + vol up and down) makes the screen flash off momentarily and then come back on again, but that's it. I can't get into recovery mode, and I couldn't get into download mode either, as the phone won't stay off when I put the battery in.
So, I bought a USB jig and to my relief it enabled the phone to get into download mode. I put the jig in the USB port and insert the battery, and download mode immediately comes up. Then I remove the jig and either connect the USB cable and then start Odin, or start Odin and then connect the USB cable. Either way, Odin doesn't recognize the phone. Windows gives me some sort of error about a malfunctioning USB device.
I know the problem is the phone, and not my cable or computer, because I can Odin to my wife's Vibrant no problem. Any ideas?
sporglak said:
I've searched and searched, but I've been unable to find a solution to, or even any examples of, my particular problem. I was wiping and formatting everything before I flashing a ROM as I've done countless times before, but this time I decided to format the boot partition, which I can't remember ever doing before, and I think I then pulled the battery before flashing anything.
Now when I put the battery back in or plug in the USB cable (without pressing any buttons at all) the phone immediately shows the Vibrant/Samsung screen and nothing else happens. Holding the power button (or power + vol up, or power + vol down, or power + vol up and down) makes the screen flash off momentarily and then come back on again, but that's it. I can't get into recovery mode, and I couldn't get into download mode either, as the phone won't stay off when I put the battery in.
So, I bought a USB jig and to my relief it enabled the phone to get into download mode. I put the jig in the USB port and insert the battery, and download mode immediately comes up. Then I remove the jig and either connect the USB cable and then start Odin, or start Odin and then connect the USB cable. Either way, Odin doesn't recognize the phone. Windows gives me some sort of error about a malfunctioning USB device.
I know the problem is the phone, and not my cable or computer, because I can Odin to my wife's Vibrant no problem. Any ideas?
Click to expand...
Click to collapse
Alrighty, well...I actually remember a thread like this coming up awhile back and having no freakin' clue personally...however it lead me to think that you ought to have done a search of the forums before posting this. I was however wrong. I've spent about the last 45 minutes reading thread upon thread upon thread dealing with this issue without any of them offering a solution. Most were simply saying things like:
G0 TRYZZ A KNEW C0RDDD N00BBBIEEE
Click to expand...
Click to collapse
or
1NSTALLZ NEW DRYVRZ U NAP
Click to expand...
Click to collapse
or even
AI0 TO0L BOXXXX S0LVZZ EET 1DIOT
Click to expand...
Click to collapse
Okay...I made that up. Our community isn't so mean lol However, those were pretty much the only solutions I came across, and sadly they did not work.
So....I'm going to take a shot in the dark and suggest you head on over to this thread and give it a whirl:
http://forum.xda-developers.com/showthread.php?p=15330252
I have not seen this suggested in any of the dozens of threads i visited, and honestly, I don't know all too much about the process, but hopefully it will work for you. Read it over, test it out and if it doesn't work head back here and let us know and we can figure something out...and who knows, maybe by then someone with far more knowledge of this particular problem will pass on through and shed some light on the situation.
But for now, concentrate on staying calm and we'll work through it.
Sounds like you deleted the boot loaders. Make sure you have correct drivers installed, windows isn't auto detecting. Try to get Odin to recognize again, try all USB ports. If you get it recognized make sure to √ re-partition.
BTW Xeno, you made me bust out laughing!
sent from my magic box to yours
---------- Post added at 02:53 AM ---------- Previous post was at 02:33 AM ----------
I just read something about this...its not boot loader just boot image. It suggested trying kies.
sent from my magic box to yours
samsgun357 said:
BTW Xeno, you made me bust out laughing!
-----
I just read something about this...its not boot loader just boot image. It suggested trying kies.
Click to expand...
Click to collapse
All in a days work! Aha!
Also, not to go against your advice, because I think its awesome that you responded and are searching for a "cure" but OP do not, I repeat, do NOT touch kies. I'm sure you've heard about the Holocaust in your history classes at some point, yes? Well that was microscopic compared to the disasters that will befall your vibrant if you bring it anywhere near the kies software. Do NOT do it. Think of the kids for God's sake. That is all.
Xenoism said:
Alrighty, well...I actually remember a thread like this coming up awhile back and having no freakin' clue personally...however it lead me to think that you ought to have done a search of the forums before posting this. I was however wrong. I've spent about the last 45 minutes reading thread upon thread upon thread dealing with this issue without any of them offering a solution. Most were simply saying things like:
or
or even
Okay...I made that up. Our community isn't so mean lol However, those were pretty much the only solutions I came across, and sadly they did not work.
So....I'm going to take a shot in the dark and suggest you head on over to this thread and give it a whirl:
http://forum.xda-developers.com/showthread.php?p=15330252
I have not seen this suggested in any of the dozens of threads i visited, and honestly, I don't know all too much about the process, but hopefully it will work for you. Read it over, test it out and if it doesn't work head back here and let us know and we can figure something out...and who knows, maybe by then someone with far more knowledge of this particular problem will pass on through and shed some light on the situation.
But for now, concentrate on staying calm and we'll work through it.
Click to expand...
Click to collapse
"Failed. Unspecified Error." Thanks for the suggestion, though, Xenoism. I knew that no matter how diligent my search of the forums, somebody would toss out a link to a post I missed.
@xeno, your killing me hahaha! I have heard about bad experiences with kies. I have used it a few times without issue, this was my Pre xda days. I figured this guy didn't have much to lose and if kies hard bricked it, he'd have a better shot of Sammy or tmo hooking him up with a fix. I guess for $40 he could get a JTAG repair.
sent from my magic box to yours
sporglak said:
"Failed. Unspecified Error." Thanks for the suggestion, though, Xenoism. I knew that no matter how diligent my search of the forums, somebody would toss out a link to a post I missed.
Click to expand...
Click to collapse
I was afraid that might not help you. I spent another hour or so this morning looking throughout the web for potential solutions...nothing just yet :/
I'll keep searching though, if you do the same man ^^
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hi all,
I thought this might help ppl, it certainly helped me.
So as I reported earlier mine NT was one of those which wont boot off of the sd unless tethered. I did many things but I THINK (can't be certain) that I did what is mentioned my the guy PHIL here in the below link and it solved it (for until now, for my last 3-4 boots)
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
P.S. : Making a separate thread so that ppl can see and get benefited. Sorry if thats against forum rules. Just trying to help
Cheers !
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
asawi said:
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
Click to expand...
Click to collapse
Hi, I see the confusion, what I meant (at least worked for me) is to that as a one time thing.. after that if I switch off switch on it can boot from sd card by pressing the n key on startup, no more need of tethering. I don't know if it'll work with everyone, don't have more such tablets to try on. Give it a shot. Worked for me, I hope this helps
firstdavis said:
Hi all,
I thought this might help ppl, it certainly helped me.
...
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
...
Click to expand...
Click to collapse
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work with any CM9 and CM10 SD ROM builds.
digixmax said:
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work when with any CM9 and CM10 SD ROM builds.
Click to expand...
Click to collapse
I didn't know about that thread, still reading all of it.. but just fyi, this method worked for me for CM10.2 (android 4.3 latest ROM)