I am rooted but I took all the precautions before the update such as unfreezing. I can't get into boot loader. No matter what kind of reset I'm stuck at the splash screen. Others have this issue and are completely stock. Any guidance is appreciated!
Have same problem coming from stock .28. Actually did a factory reset before update and it looked like update worked fine. Haven't been successfully able to boot into jelly bean. Can't even power off
same problem
me too stuck in to boot screen (asus logo on center nvidia logo in right bottom corner)
after jell bean update !
I'm there too - used Protato's method to the letter (I thought) - it looks like a brick, doesn't it.
OMG asus replied me
Dear Sir/Madam,
Thank you for contacting ASUS Technical Service.
Hi, I'm very glad to help you. For the problem, please try to hold the power button down for 10-15 seconds to reboot the device.
If stills, I suggest you follow the instructions below to perform “Wipe Data” to restore the unit back to the factory default condition.
Warning: Wiping data will erase all user data. The data is irrecoverable after the wipe.
1. Press and hold down “power button” until the system shuts down.
2. Remove the SD card from Eee Pad.
3. Press and hold down “Volume down” button first, and then press and hold down the “Power” button until the below words appear on the screen:
“Checking for RCK..press key in 5 sec to enter RCK”
4. Do not press any button until there is a line “Press to execute, to cancel wiping data.” Press Volume Up button to execute the “Wipe Data”.
5. After the “Wipe Data” process is done, it will reboot automatically. Then Eee Pad should be able to enter the system successfully.
Click to expand...
Click to collapse
problem is device not closing with power button. only restarts itself. volume up + power button closes screen but device still active because apx driver appears in my pc with universal naked drivers.
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Selhati said:
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Click to expand...
Click to collapse
Do you think they will care if its rooted at this point? I want to RMA mine now this is just the cherry on top. I opened up my prime before but didn't tweak it at all. Hopefully I won't get a 300$ bill after this.
Has anyone figured out how to get pass this issue?
Has anyone figured out how to get pass this issue?
Stuck on splashscreen
I am also experiencing the same issue with my Prime. My tablet had flashed Jelly Bean without a flaw while rooted with a deodexed file I found from one of the developers. It worked great throughout the day and it remained rooted but when I decided to reboot my tablet, it got stuck in the splash screen. Now it will not boot up at all. It is just stuck on the Asus splashscreen. I hope someone figures out how to fix this issue.
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
they'll RMA it for free even if you're rooted/unlocked. they have no way of telling.
EZPIMP69 said:
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Click to expand...
Click to collapse
I think if everything goes to crap, I'll get a Nexus 7. It's really going to hurt not having a keyboard dock since I use my Prime as a laptop. Reason why I don't really want to get an infinity is because Asus still hasn't ironed out all the issues with the Transformer line. Plus if I hork out another $500 and get burned by a new product come Christmas, I am not going to be happy. Hoping that my Prime will be ok but ya, the worst usually happens to me.
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Any new ideas on how to get this fixed? Stuck on the Asus splash screen alo.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
Well I tried the steps in the link provided but had no luck since it requires fastboot. My tablet won't turn off or go into fastboot. The only way I think we can repair this is with NVflash but Asus needs to provide the files needed to complete a factory flash. This **** sucks.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
So what was the result?
Count me in
Just another report of this happening to me. Stuck in the Asus "perfection" logo.
The only thing I have found is that I can turn off the screen following this steps:
Connect it to the power
With a pin press and hold the reset button
Keeping pressed the reset button disconnect the power connector,
Connect the power bak again (always pressing the reset button) and wait about ten seconds before finally release the reset button.
At least now I don't see that dreadful screen reminding me that I have an useless glowing brick in my desk.
Hopefully someone finds a way to unbrick it because I will be costly having to RMA the prime back to the US where I bought it.
T-HO6969 said:
So what was the result?
Click to expand...
Click to collapse
It did not work since I can't boot into fastboot to begin the process.
Let's collect info about the problem.
Let's try to find a common issue of why we got bricked answering some simple questions and hoping someone with better knowledge can use this information to help us. Here are some questions, you can add any information that you consider relevant.
How did you upgrade to JellyBean: I used this method
Unlocked? NO
Rooted"? YES. Because it was necesary in order to update to JB using the procedure linked above
Additional relevant info: My prime have the famous "unknown serial" problem that was never resolved by ASUS. Because of this, it has never received OTA and always have been updated with the firmwares from the ASUS website. This time instead of waiting for ASUS to publish JB in the support website I used the procedure above. Appart from this I have always keep it "stock".
Related
So I plugged my Vibrant into Odin to revert to stock. Apparently everything went wrong, and now my phone is stuck at the Phone---!---computer screen. It seems that my phone won't respond to hardware methods of entering download mode, so am I screwed?
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
I've tried that, and many other methods, multiple times already. It seems that none of the volume/power methods do anything for my phone. I'm certain that if hardware-locks do exist for certain vibrants, mine just so happens to be one of them (Date on box is August 13). I just want to know if anyone with a similarly dated phone has ever been able to access download mode without adb.
If anyone knows of more methods, please post them. If all else fails, I'll go complain in my local T-Mobile store that my phone died. I have no idea if that'll get me anywhere, but it's worth a shot.
Does anyone who has had a problem similar to mine know of any fix? By that I mean, has someone who has had a presumably hardware-locked phone ever been able to boot it into download mode without adb? I'd really like to know if I can salvage this thing, or if I have to try my luck with T-Mobile.
Try holding volume down and holding power button and plug in USB while this is happening.
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Generic112 said:
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Click to expand...
Click to collapse
When you see the " !---> (pc)" symbol, plug your USB in. Hold down volume +, volume -, and power. As soon as the screen turns black release the power button only. Continue holding Vol + and Vol -. You'll enter Download mode.
I've tried that multiple times, but I will continue to try it. It seems as though my phone won't register that buttons are being pressed. All that happens is the phone reboots to the Phone--!--Computer screen every time the power is held and released (As it should). No combination of buttons seems to have any affect on this. Oh well, I'll continue trying and hopefully someone will post a working method.
I have the same problem and the hardware button method isn't working and I am stuck at the Phone ! Computer screen, and I read around the forums and they say that some Vibrant's have the hardware method locked, so you can't boot into Download mode from using the buttons. Since adb cannot find the phone when its stuck at this screen it seems we are both screwed. I have found no other solution other than returning it Tmo, not sure if they will exchange since it might be a violation of warranty.
I'm just going to play dumb when I go to T-Mobile. I'll say it just booted into that screen, and I can't get out of it. The hardware lock appears to be a defect, since it's not present on most Vibrants, so that should be able to warrant the replacement phone. I've been with T-Mobile awhile, and they're usually pretty good with replacements. Besides, the phone would be easily fixed if it wasn't broken in the first place.
But before I go to T-Mobile, I'm going to try and talk to Customer Service. If it's a common problem, then I'm sure it can be covered under warranty (Even though MOST ways of getting it require voiding warranty). Again, on the basis that this wouldn't be a big deal if my phone worked like a normal Vibrant. Besides, I'm sure T-Mobile can flash it without requiring the hardware method, so even if they only charge me some sort of service fee, I won't really mind.
As final moral reassurance for myself, I only tried to flash it because apps started FC on me and the phone constantly acted weird. The only thing I've done is root it, so it's not like I really set it up to fail.
Let me know how it goes with Customer Service. I would to get this problem resolved as well with the least amount of trouble. I don't want to have a brick and have to pay like $500 for a new phone. And I think the hardware buttons thing might actually be a defect. I tried doing the hardware buttons thing to get to recovery mode once before and it worked. I did this to install an update.zip to root the phone. It only worked that one time and now the buttons don't boot into recovery mode or download mode. It if works once then not again, there has to be something wrong.
I'll be trying them tomorrow (It's 10PM where I am). If all goes well, I'll try and contact you. I'm pretty sure I'll be safe so long as I don't mention rooting it. The firmware flash they'll have to do should help me on that front, so unless they catch on, I should be safe. Anyway, hopefully tomorrow I'll be good news, otherwise expect some post from me on Monday or Tuesday, depending on whether I have the time to deal with them or not.
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
I am also struck with the same problem
Hi,
I am also struck with the same problem. Please let me know if you guys got any method to resolve the problem or T-Mobile was able to help.
the3dman said:
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
This method actually worked for me. I was beginning to think I'd have to build the USB jig, but tried this as a last ditch. Thanks!
The above method has worked for me numerous times with the same problem, my old bricked one, and my new one. Try holding down power button as well once or twice, never know. You have to keep the volume buttons pressed the whole time for it to work.
Sent from my SGH-T959 using XDA App
ViralCipher said:
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
Click to expand...
Click to collapse
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
ech419 said:
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
Click to expand...
Click to collapse
He should be able to get the phone woking again, what happened is not a big deal. If he sends it in the way it's sitting right now, t'Mo's techs won't have a problem getting it working again. (IMO) Especially if they find out the phone's rooted, I wouldn't be surprised if he gets charged.
I bricked my phone so bad, it was beyond recovery. I erased the bootloader, therefore it was completelly dead. No life. I got a replacement under warranty for free, never got charged for it.
My advice would be to try and get to work again before sending it in.
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!
I dropped my phone a few days ago and the power button stopped working. Reboot ed into recovery from Rom Manager and realized that I couldn't select anything because I need the power button (tried every other button as well; nothing works). Took the battery out and put it back in (the only way to turn it off now) and it instantly booted into recovery. I can't send it to AT&T because I have at least 10 counts and they'll instantly see that CWM is on there.
Please help me!
kancheek1995 said:
I dropped my phone a few days ago and the power button stopped working. Reboot ed into recovery from Rom Manager and realized that I couldn't select anything because I need the power button (tried every other button as well; nothing works). Took the battery out and put it back in (the only way to turn it off now) and it instantly booted into recovery. I can't send it to AT&T because I have at least 10 counts and they'll instantly see that CWM is on there.
Please help me!
Click to expand...
Click to collapse
You dropped your phone. Samsung/AT&T warranty doesn't cover accidents, so there's no sense in worrying about your flash count. You're SOL. But you are free to try of course. Reverting to stock is very easy. What would you even do in recovery mode to revert to stock? Did you bother to look around the forum? There is a guide in the general forum on how to do that.
Out of curiosity, I did a google search to see what the repair options were for a broken power button. Saw that Mobile Tech Videos does it for $35 + shipping. Might be one of the better options at this point. As for the counter, just buy or make a jig to reset it.
mzaur said:
You dropped your phone. Samsung/AT&T warranty doesn't cover accidents, so there's no sense in worrying about your flash count. You're SOL. But you are free to try of course. Reverting to stock is very easy. What would you even do in recovery mode to revert to stock? Did you bother to look around the forum? There is a guide in the general forum on how to do that.
Click to expand...
Click to collapse
They wouldn't know that I dropped it unless I told them that, so as of right now the button stopped working by itself. I reverted to stock a while ago when I thought I bricked it, but I need to get it into download mode which can't be done without the power button.
kancheek1995 said:
They wouldn't know that I dropped it unless I told them that, so as of right now the button stopped working by itself. I reverted to stock a while ago when I thought I bricked it, but I need to get it into download mode which can't be done without the power button.
Click to expand...
Click to collapse
Recovery mode requires the power button. Download mode only requires the two volume buttons. With the phone off, while holding down vol- & vol+ plug in USB cable.
Lawrence of a Labia said:
Out of curiosity, I did a google search to see what the repair options were for a broken power button. Saw that Mobile Tech Videos does it for $35 + shipping. Might be one of the better options at this point. As for the counter, just buy or make a jig to reset it.
Click to expand...
Click to collapse
Good info if I ever need this
Has anybody used mobile tech videos to get their power button fixed? Mine stopped working out of the blue today, my phone is long out of warranty, and it refuses to connect to my computer at all so I can't revert to stock (I'm running AOKP 6.27.12 Build right now). I don't want to just send my phone off to some place that isn't reputable.
elementlaxer said:
Has anybody used mobile tech videos to get their power button fixed? Mine stopped working out of the blue today, my phone is long out of warranty, and it refuses to connect to my computer at all so I can't revert to stock (I'm running AOKP 6.27.12 Build right now). I don't want to just send my phone off to some place that isn't reputable.
Click to expand...
Click to collapse
It's still got to be in warranty with Samsung. The first units were shipped just under 9 months ago.
Mobile tech videos is considered to be quite reputable. I have only seen good reports about them, and the owner posts actively on the XDA-Developers boards.
You should be able to enter download mode. You don't need the power button for that.
Darn I didn't realize how long Samsung's warranties were. I made the switch back in October from Apple products so I'm used to crappy warranties.
I've already shipped to mobile tech videos because I searched around the forums a bit and found out that he is in fact reputable.
And I know how to get into download mode, I can do that no problem. My computer always pops up saying there is some problem with the device and I'm not sure how to fix it. I have the drivers installed correctly and it has worked in the past, but not recently. I would try to replicate it now but I don't have the phone in my possession, and at the moment it isn't really causing me an issue.
If you can't get Odin to recognize the phone once connected to the computer in download mode, then it is most likely a driver problem, or less likely a problem with the USB cable or ports. Once you get the phone back, if you still have the problem, that is where to look first.
I just wanted to point out that the broken power button would not prevent you from returning the phone to stock, although it can be a bit of a problem that you can't use recovery.
Yeah I was a bit worried that if I tried to go through Odin and something got messed up I wouldn't be able to get back into recovery to restore from a backup.
Thanks for all the help! I feel like a total noob and I appreciate your patience haha
In case you haven't already tried, in some versions of CWM (even non-touch) the search button (softkey) works like enter. Try all of the softkeys, one of them might work for you.
Yes, but if you Odin back to stock with a broken power button, that leaves you with stock 3e recovery. Even if you use adb reboot recovery to get into 3e recovery, you can't select anything without the power button.
Hello guys,
I have (had) a transformer prime with stock android 4.1.
I tried to flash my Prime with Goomanager and TWRP.
I found out that I had to install twrp manually to do this. (it was disabled by goomanager for the prime)
So I rooted my tablet with motor chopper, unlocked my bootloader with the asus apk and followed these instructions http://www.youtube.com/watch?v=0-KLPDu2sos
They looked pretty straight forward, so I thought I'd give it a try.
I downloaded the file and relocated it to /twrp.blob and typed "reboot".
After rebooting I used goomanagers "Restore Recovery" button and after that it wouldn't boot.
It always freezes at the boot screen. (the one with the asus Logo in the center and Nvidia logo in the right bottom corner)
It also says "The device is unlocked." in the left upper corner.
I didn't know that I would need ADB (i didn't even know at that time, what that was) or fastboot on my laptop. Maybe this is my problem.
I tried the follwing things:
- press power and lower volume:
the tablets just turns off and on to this same splash screen
- I thought about trying option 1 from here (http://forum.xda-developers.com/showthread.php?t=1514088), but I had to install adb and fastboot, but when I type "adb devices" in the console, it says "list of devices attached", but there aren't any.
(my tablet is connected and is turned on [at least to this splash screen])
I hope you guys can help me and I didn't brick my tablet completely.
thanks
Simon
Same exact thing happened to me. Tried to reboot into recovery and now I can't get past the splash screen. No option for fastboot and adb does not show my device. I had to send mine in to Asus and that was three weeks ago. They have informed me that there will be a charge (have not said how much yet) but other than that no response from them. The issue we are having is a hard brick and unless you backed your prime up with nvflash? tool before upgrading to Jeallybean there is no way to recover it.
Hi @slatonyam,
thank you very much for your answer.
Could you please be so kind to tell me what it cost to repair it, after you got it back?
I just want to make sure it is worth the trouble and money.
Isn't there another way by using a micro sd with a build or similar?
best regards
slatonyam said:
Same exact thing happened to me. Tried to reboot into recovery and now I can't get past the splash screen. No option for fastboot and adb does not show my device. I had to send mine in to Asus and that was three weeks ago. They have informed me that there will be a charge (have not said how much yet) but other than that no response from them. The issue we are having is a hard brick and unless you backed your prime up with nvflash? tool before upgrading to Jeallybean there is no way to recover it.
Click to expand...
Click to collapse
Simon after three weeks of sitting on my tablet and numerous phone calls and emails from me, Asus finally got back to me with a quote. I believe the only reason they got back to me is because I told them to ship my tablet back to me and forget the repairs. This is the quote they gave me:
$213 for the motherboard
$65 for labor
I had already told them to ship my tablet back to me so I wasn't interested in getting it repaired and the cost is too much. I only paid $249 for the tablet through New Egg. So I think I just might buy a motherboard off ebay and try to repair it myself, I figure I have nothing to lose.
SimonErich said:
Hi @slatonyam,
thank you very much for your answer.
Could you please be so kind to tell me what it cost to repair it, after you got it back?
I just want to make sure it is worth the trouble and money.
Isn't there another way by using a micro sd with a build or similar?
best regards
Click to expand...
Click to collapse
Update after 3 days or so waiting for them to ship my tablet. I received a email Tuesday stating that they were finally shipping my tablet back. But under the serial number I noticed that the device they are sending begins with CA whereas the one I sent in begins with a C1. Maybe they replaced my tablet after all. Will let everyone know when I receive it Tuesday.
Hi @slatonyam
I did sent my Transformer to Asus exactly 7 days ago and just got it back.
(had to send it to Asus Czeck, because I live in Austria - but it was pretty fast)
it is working again (got the same device) and it seems like they repaired it on warranty, because they didn't sent me a payment information or anything.
just got a working device back today.
I'm happy and I wish you good luck with your device.
best regards
Thanks for your kind words but I received the tablet back today and it was not repaired. But so happy that you received a repair for yours. I guess I will just lean on my Nook HD+ for now until a solution is released.
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Don Karnage said:
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Click to expand...
Click to collapse
Sorry for your troubles. Fastboot (aka factory) cables are useless on an HDX. If you can't 'see' your device via a standard usb cable or it shows up as "QHSUSB_BULK" then you're done. If the device was purchased within the past 12 months there is a good chance Amazon will exchange it for a refurb. Just say it died during an update (apparently true). No need to mention the prior root attempt which may or may not be related. Call and be nice to the rep; ultimately it's their decision.
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Don Karnage said:
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Click to expand...
Click to collapse
Those are encouraging signs. Do you recall enabling adb? If so there may be a way to revive your device via tether but the the commands/techniques are a little beyond me (others can probably help). Most require root access which you likely don't have. Best guess is the root exploit you tried was partially successful and may have altered some files needed to process ota updates. A factory reset emulates portions of that process likely resulting in the boot loop. If the offending 'update' file(s) can be renamed you might be able to boot successfully.
Don have you ever used ADB? If so this might possibly save you
http://forum.xda-developers.com/kindle-fire-hdx/general/unbrick-solutions-t3059733