Extra Unbrick Tip - Asus Eee Pad Transformer Prime

Hey, please make this a sticky(just in case someone else is freaking out like I was). I had the CWM boot loop issue and was not able to get ADB working on my device. I ended up uninstalling the device/driver and using a proxy Android Device to get it in, then reinstalled the Asus drivers. After that, it worked! Not sure if it works for every one BUT it was at least a good thing..
P.S. DO NOT USE REBOOT IN TO RECOVERY, IT'S DANGEROUS. TURN DEVICE OFF AND GO IN TO RECOVERY BY PRESSING VOLUME DOWN AND POWER, THEN VOLUME UP WHEN PROMPTED!

What thread were you posting on? I'm curious.
sent from my i9250

Post this in unbrick sticky thread.
This thread is being moved to the general section.

Related

HELP!!! Clockwork partition problem

Hey all.
I got a problem. I opened Rom Manager and did the partition SD card thinking it was going to partition my external SD card.......well, I think it did the internal. Now when I boot I get to the GalaxyS screen and then the screen just goes black. Have to remove battery to reboot. I have tried ODIN to restore a factory image but it does the same thing. Anyone have an idea. How can I just format the internal memory to factory and restore to factory. Thanks!!!
There you go
Hey man... You're gonna get flamed for this, it's one of the things "everybody" knows not to do with RomManager, but since I did the same mistake back in time I'll help
First off: can you get into download mode? (turn your phone completly off, plug it into your pc with usb, wait for the "charging" screen, then press both volum keys + the powerbutton to restart, release the powerbutton immediately after restart and keep holding the two volumekeys till you enter download mode)
then flash this.
Then flash back to stock, or any other ROM that includes kernel...
/edit
And please read some instructions this time (couldn't help it, haha)
Novek said:
Hey man... You're gonna get flamed for this, it's one of the things "everybody" knows not to do with RomManager, but since I did the same mistake back in time I'll help
First off: can you get into download mode? (turn your phone completly off, plug it into your pc with usb, wait for the "charging" screen, then press both volum keys + the powerbutton to restart, release the powerbutton immediately after restart and keep holding the two volumekeys till you enter download mode)
then flash this.
Then flash back to stock, or any other ROM that includes kernel...
/edit
And please read some instructions this time (couldn't help it, haha)
Click to expand...
Click to collapse
Thanks bro.
I normally read and research tons before I do anything. Just tried to rush through this one. Lesson learned.
I will read up now
Zero problemo ;P
Thread moved to the Q&A sub-forum. Please post questions in that forum from here on.
Thank you
I hope you were able to fix the problem.

[Q] Boot Loop on LE I/O 10.1 need help!

Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do

[Q] Accidentally installed CWM without wiping anything!

Hello devs, thanks for taking a look at this...
Well, you sort of know my question from the title.
I went into recovery mode, "install zip from sd" (and didn't wipe anything), then I restarted system.
-Now it has a boot loop.
I made one of those jigs without cutting up USB thing, hasn't worked for me yet
Specifics:
Device - AT&T Captivate
NO DOWNLOAD MODE OR RECOVERY WITH THE BUTTON FIX
ADB running and working on computer
(By the way, on my last rom, i tried using ADB to boot into download, but it didn't work?? Maybe I have no download mode available?)
Maybe this helps you:
smokestack76 said:
Works every time for me if i power off. Hold down volume up and down and power. Wait for the att screen to go off and as soon as it comes back on the second time let go of the power button and continue holding both volume button down until you see recovery booting. It works the same with a usb cable plugged in for download mode.
Click to expand...
Click to collapse
For the download mode I found this fix:
http://tips.developersvoice.com/how-to-unbrick-the-totally-bricked-samsung-captivate.html
dvasavda said:
Hello devs, thanks for taking a look at this...
Well, you sort of know my question from the title.
I went into recovery mode, "install zip from sd" (and didn't wipe anything), then I restarted system.
-Now it has a boot loop.
I made one of those jigs without cutting up USB thing, hasn't worked for me yet
Specifics:
Device - AT&T Captivate
NO DOWNLOAD MODE OR RECOVERY WITH THE BUTTON FIX
ADB running and working on computer
(By the way, on my last rom, i tried using ADB to boot into download, but it didn't work?? Maybe I have no download mode available?)
Click to expand...
Click to collapse
try booting into recovery and wiping dalvik cache that works for me when i get bootloops after installing update.zips
No luck guys,
I would do that wipe thing, if I can boot to recovery...
I tried the download mode thing... No luck
You think there is a way to freeze my phone at its state?
I can hear the USB connected sound when my phone boots, but the boot goes too fast for it to load the phone.
Did you try booting holding power on and volume key up? Also power on and volume down? Usually works when I get a boot loop.
Nope, eh, tried it many times.
Still not going to give up though
Thanks guys
So, nothing else? Eh... It's fine
Btw, how you become senior member?
senior member = 100 posts
How to shut down a thread?
dvasavda said:
How to shut down a thread?
Click to expand...
Click to collapse
PM the board's moderator
Sent from my HERO200 using XDA App
Hmm, moderator? What do you mean?
By the way, just to become a senior member, can I make a new thread and keep posting blah blah? Then delete? Hehe...
dvasavda said:
Hmm, moderator? What do you mean?
By the way, just to become a senior member, can I make a new thread and keep posting blah blah? Then delete? Hehe...
Click to expand...
Click to collapse
moderators have the power to edit/delete posts/threads. only they can delete. and if they see all that spam, they might even ban you (at least temporarily)
Oh poop
Hey btw, do any of you both know of my scenario? Cyanogen without wiping... Both of you
Not sure, my device is almost impossible to mess up haha. But if you had cwm on your phone and were able to flash a zip, how come you can't boot to recovery again; wipe what you need and flash the zip again?
I don't see how flashing a zip would mess with your recovery partition, unless you were flashing another recovery.
I'm not familiar with your device, so I would recommend looking at your device's forum, instead of General Android.
Sent from my HERO200 using XDA App
Last time, my phone wasnt in a boot loop, it just froze at the galaxy s screen, so, I was able to plug to computer and ADB it; but this time, i can hear the connect sound on computer, but it takes a bit time to load the drivers for the computer, but by then, the phone has restarted
dvasavda said:
Oh poop
Hey btw, do any of you both know of my scenario? Cyanogen without wiping... Both of you
Click to expand...
Click to collapse
look through all of the stuff here:
http://forum.xda-developers.com/search.php?searchid=84776944
i cant exactly help you because my phone doesnt have a download mode, and i would recommend using fastboot but your phone doesnt have fastboot
i would buy a jig, but i cant...
if i ever get enough convince...
http://cgi.ebay.com/Download-Mode-fix-USB-Jig-Samsung-Galaxy-S-Phones-/130556502027#ht_3633wt_1164
you think this will work on my situation, and this is real?
-btw, can android ever: never have a download mode?
thanks

rooted phone OTA

I have a rooted artrix and the other night i updated via OTA and now the phone wont boot. how can i fix this? any help would be nice
Yeah, that sounds about right. Can you get into rsd mode or anything??? Btw, please post this in Q&A. You will more than likely get flamed for posting in the wrong section.
#Sent from my God given Atrix 4G
i tired booting into recovery and iot says starting fastboot protcol support
There are lots of tutorials on here on how to unbrick your phone (depending on hard brick or soft brick)
Look through the Q&A section - http://forum.xda-developers.com/forumdisplay.php?f=1070
If you get an error message on your screen during regular boot, use the search tool in that forum to search for what it says. That should help narrow it down.
BTW: When booting into recovery, make sure you Hold Vol + down until it says "fastboot" on the screen, then press Vol + down until the words say "Android Recovery" and then press Vol + Up.
Warrior 3000 said:
I have a rooted artrix and the other night i updated via OTA and now the phone wont boot. how can i fix this? any help would be nice
Click to expand...
Click to collapse
try this my friend and good luck : http://forum.xda-developers.com/showpost.php?p=22583493&postcount=139

Download Mode and bootloader

Hi guys! I've been having problems with my Mega. My phone works really fine. I just got it the other day. But whenever I try to go to download mode or recovery I only get a blank screen but I know that it goes to download or recovery because my phone could detect it. I've been reading some forums that I have to reflash the bootloader of my phone so I could fix that error. Does anyone here confirm this and could anyone provide me a flashabble copy of the bootloader? Thanks!
Here's what I found on the other forums:
makeyourself said:
Your problem sounds similar to this one. I assume when you say 'blank screen' that the screen is powered on?
Power off the phone, hold down VolUp + VolDown + Power for 4 to 5 seconds. Then release ALL AT THE SAME TIME. Now press Volume Up. Now hopefully you will be in download mode even if you can't see that you are. If it doesn't work try it again a couple of times. The reason that you have to press Volume Up is that a warning screen is actually displayed before the phone lets you into download mode.
The phone will give you no other indication that its in download mode and won't 'recognise Odin' when not in download mode. Make sure you have Samsung USB drivers (comes with Samsung Kies) installed on your PC.
Oh yeah and by the way the thread I've linked to suggests you have to reflash the bootloader to fix the 'blank screen' problem.
Click to expand...
Click to collapse
Mods, could you delete this thread? i've move it to the android development forum. Thanks! Sorry for the inconvenience
You where correct to keep this thread here, vice posting in the Development threads....this one is closed and I have moved your other thread from the Dev Sections to this section.
Thread Closed

Categories

Resources