Hey guys,
I just wanted to put some information together on how to recover your bricked Prime (if possible).
DISCLAIMER
I am in no way responsible for what you do with your Prime, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
Currently we know 4 states of bricked Primes whereas 3 are more or less widespread.
Brick 1a: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now it always boots into recovery instead of your ROM.
You can't select to boot to fastboot or anything else. No matter what you do it's always the recovery. (happening to many users)
-> Please go to Option 1a
Brick 1b: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now once you want to boot your new ROM it shows you the bootanimation but suddenly tells you something about an "unsuccessful encryption" (it's a real android screen, with a touch button etc.)
Once you hit the "Reset" button it restarts but you can't boot the ROM anymore, you are now caught in a CWM loop (much like Brick 1a)
-> Please go to Option 1b
Brick 2: When booting up your Prime hangs at the splashscreen (the screen with "EeePad" in the middle) and tells you something about an "unrecoverable bootloader error" (happened so far to at least 4 users)
-> Please go to Option 2
Brick 3: (After messing around with your Prime in recovery it won't boot any ROM anymore, you can however still access fastboot and the recovery)
Update: This particular brick happens due to a bad kernel flash. If you are flashing kernels via the ASUS /staging method, make sure /staging is unmounted before flashing stuff to it, otherwise it WILL faill and brick.
Update 2: It seems we can't use the old fix for this brick anymore. Sometimes it does more bad than good.
->Please go to Option 3
Option 1a
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Option 1b
Good news, this brick should be no problem.
Basically you need to first do Option 1a, but don't reboot the Prime just yet.
After executing the dd commands, you need to reboot your Prime to the bootloader menu and NOT the ROM itself.
To do this you need to reboot your device while holding down the Volume_Down key.
Once the white text in the top left corner appears release the buttons.
Now don't press anything until you can see a menu with 3 icons, an Android symbol, an USB symbol and a Wipe Data symbol.
Select the Wipe Data icon with pressing Volume_Down twice. Now press Volume_Up twice to reset the device to factory state.
WARNING: OF COURSE THIS WILL DELETE ALL YOUR DATA!!!! EVEN THE INTERNAL MEMORY AKA SDCARD!!! CURRENTLY I DON'T KNOW ANY OTHER WAY TO RECOVER FROM THIS BRICK!!!
After the wipe is done, you should be able to flash a new ROM or boot the existing ROM
Option 2
Sorry, but your Prime is most likely hard bricked.
This can happen if you try to apply a stock blob file after you installed CWM. There is currently no way to recover from this.
Option 3
If you are in this situation (Prime doesn't boot but you can access both recovery and fastboot) please go to #asus-transformer on freenode and ask for help there. We currently don't know if you can recover from this state.
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
We now found a way to un-brick this one too
This one is a bit more risky, so make sure you follow all instructions with a bit of extra care.
Update: It seems the old method for this brick could make things even worse on some Primes.
On some primes this can be easily fixed, however putting this in a guide could do more harm than good.
Troubleshooting
Problems getting ADB to work in recovery mode? Only seeing something like "Full Android on Emulator" in the device manager instead of your tablet?
Well I have a posible fix for you: Got to this thread and download the drivers. Then override the drivers for the Emulator device manually with the new ones. ADB should work now
--- Read here how to prevent future bricks and other common problems ---
Bits & pieces
You might want to have a look here for a possible solution for some bootloader errors (It's from a TF300):
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Credits:
thx to kmdm for his solution on Brick 1a and Brick 3
Sticky!
Sent from my Transformer Prime TF201 using xda premium
Thanks OP, now ive muster up the courage to root it and do everything else that's nice to it!
Thanks for the guide, very helpful. So I take it yours is still hard bricked?
Sent from my Transformer Prime TF201 using Tapatalk
Ultraman666 said:
Thanks for the guide, very helpful. So I take it yours is stuck on option 2 ?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
yes...
Update on a 4th option coming soon
Dude that sucks, hope you find a way to reverse it. Good luck
Sent from my Transformer Prime TF201 using Tapatalk
guy, come to diamondback channel so he can help you, seriously, he is so helpful, i cant even sleep for the whole night to figure out my problem, but after 10 mins with him, my tablet ready to rock and roll now, ty so much....
Any hope for JTAG?
Okay I added a 4th brick to the list. It's a variant of the first Brick and it is recoverable
How horrible would it be for Asus to provide the equivalent of odin for our devices?
I don't see what's so hard with embracing development.
You've got my back.
Thank you Diamondback. It's comforting to have this info available before I take the plunge.
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
Well because you can do way more stuff with Android phones
Ever run a different OS on the iPhone? Not that I am aware of
It's like having a full blown PC with BIOS and all versus having a Nintendo 64
Ever bricked a N64?
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
As Diamondback said, it's simply because we can do more with Android.
Rest assured that if the same type of modifications could be made to IOS, the risk of "bricking" would be the same.
A big help would be having a ported nvflash tool, or Smartflash.... Saved many guys on other Tegra devices like my phone for example.
chugger93 said:
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Click to expand...
Click to collapse
This is a product of the Android fragmentation. Every device is different and uses different hardware/drivers. The Android OS assumes you know what you are doing and will actually let you do what ever you want. If you flash a ROM/Firmware that is designed for the Nexus on a Galaxy S II it will let you, you will brick the Galaxy S II, but it will let you do whatever you want.
That is also why everytime Google releases a new version of an OS it takes so long to apply it to all the different devices. The moment ICS was released, it was not compatible with every device out of the box. Every manufacturer has to create drivers, kernels, and libraries for it to work on their device.
You cannot brick an Iphone because it only has 1 OS to install and only 1 type of hardware to cater to
Good Read about the effort that goes into rolling out a new OS for the android space: http://www.extremetech.com/computin...nths-to-deliver-android-updates-to-your-phone
P.S. +1 to sticky
Does APX mode work in Option 2?
STICKY THIS! Very important information. Thank you Diamond Back and hope the best for you and your Prime
REAVER117 said:
Does APX mode work in Option 2?
Click to expand...
Click to collapse
Yes but that doesn't help anything thx to ASUS' encrypted bootloader partition....
This is a good thread, I hope to never need it.
The closest I've ever come to 'bricking' a device (or at least so I thought) was practically my first experience with android modification:
Rooted and Installed CWM on my Droid Incredible. Initiated install of a Rom from Rom Manager. I Had not realized that the Dinc had 2 different screens, AMOLED and something else. CWM was not configured to display anything for my type of screen! so I had a failed rom install and no visible CWM to do any recovery (womp womp). But did some research and some guys from the CM irc helped me use the google sdk to get up a snapshot on my computer of what was happening on my phone. BAM was able to see the recovery on my laptop and install a fix for it Was pretty scary.
Glad there are people like you out there to help others out when scary and rather Traumatic experiences like this happen
Related
Hello and thanks to take care about this thread,
When I tryed to install CyanogenMod, the internal storage was moved from /dev/block/mmcblk0 to /dev/block/mmcblk1.
Fortunaly I could access to the adb and fastboot interface.
So I used './adb shell' then 'dd if=/dev/block/mmcblk1 of=/dev/block/mmcblk0 bs=4096 conv=notrunc,noerror' to restore the first partition, but during the process, the asus transformer prime shuting down (no more baterry ?) and now i can't access clockworkmod, i can't see the splach screen, i think the mmcblk0 is corrupt but no empty, and i can't acess fastboot or adb.
The last interface avaible is the apx nvidia device who is recognise when i log the tablet on the computer, it's possible to do anythink with that ?
With hope
Scarilan
The dd command that you have in your post will overwrite everything in mmcblk0, not just the first partition. The internal storage that is used by android as the data partition is mmcblk0p8, a partition on the block.
That being said, the first few partitions are extremely important in order for tfp to work, which include the bootloader and boot configuration table. Corrupt these and you will have a brick.
Nvflash would be the only way to recover, however the only available way to use this is to create device specific files PRIOR to bricking.
Unfortunately in your situation, it would appear from what you have posted that you have corrupted your bootloader, and will not be recoverable, only unless you have done the wheelie/nvflash procedure prior to your current state.
Sent from my SO-01C using xda app-developers app
I didn't execute this procedure before my state, should i return the device to asus or it's existing a procedure with the sdcard or an other with the use of nvidia who can help me ? I never learned much about android before this story, but it was a costly took had a lack of knowledge apparently.
There are any escape ?
-> Edit :
I have an idea, Can i access to the storage with ubuntu ? If i can mount the HDD on ubuntu, i could regenerate the partition and solve my problem.
If it's possible, can i mount the hdd with the nvidia apx on my computer or is it required to open the tablet ?
Scarilan said:
I didn't execute this procedure before my state, should i return the device to asus or it's existing a procedure with the sdcard or an other with the use of nvidia who can help me ? I never learned much about android before this story, but it was a costly took had a lack of knowledge apparently.
There are any escape ?
-> Edit :
I have an idea, Can i access to the storage with ubuntu ? If i can mount the HDD on ubuntu, i could regenerate the partition and solve my problem.
If it's possible, can i mount the hdd with the nvidia apx on my computer or is it required to open the tablet ?
Click to expand...
Click to collapse
hey mate..can you tell me what happened with your tablet? because i've exactly the same problem. Moe
0din said:
hey mate..can you tell me what happened with your tablet? because i've exactly the same problem. Moe
Click to expand...
Click to collapse
If you have done the same as the op, there is no way unfortunately that you will be able to restore this device yourself, unless you took the NVFlash backup prior to it breaking, (and backed this up somewhere other than your tablet).
effectively, you will have wiped every partition off the MMC including the bootloader. this would leave Nvidia APX mode as your only route to restore, Asus have locked out this functionality, however if you were prepared and did the nvflash backup, this works around the lock that asus put in place.
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
rosebud said:
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
Click to expand...
Click to collapse
I sent the tablet to Asus. It was restored and I didn't have to pay the cost of repair. It's the luck or Asus is a very good company. I hope you'll solve your problem.
Thanks to Asus and to all the member of XDA
Scarilan said:
I sent the tablet to Asus. It was restored and I didn't have to pay the cost of repair. It's the luck or Asus is a very good company. I hope you'll solve your problem.
Thanks to Asus and to all the member of XDA
Click to expand...
Click to collapse
Repaired or changed the motherboard from ASUS ?
Asus repair the device. I have sent only the tablet (no the dock) and I have received it after one week. I don't know why but Asus joined with the device a micro-usb card of 16go (that was not my card of 32go, removed before sent my tablet). I won 16go with this story (i take care about virus, don't worry for that )
rosebud said:
If you have done the same as the op, there is no way unfortunately that you will be able to restore this device yourself, unless you took the NVFlash backup prior to it breaking, (and backed this up somewhere other than your tablet).
effectively, you will have wiped every partition off the MMC including the bootloader. this would leave Nvidia APX mode as your only route to restore, Asus have locked out this functionality, however if you were prepared and did the nvflash backup, this works around the lock that asus put in place.
If you didnt do the NVFlash backup, ASUS are your only hope (and they will likely charge for the privelage)
Steve
Click to expand...
Click to collapse
I have similar symptoms as the OP, although I didn't really do the same things as him.
Here's what happened to the best of my memory. I had my tablet running the official jellybean OTA with no problems. I unlocked the bootloader using ASUS' tool. I then rooted using the modified debugfs method (http://forum.xda-developers.com/show....php?t=1706588). At this point, the tablet seemed stable and I confirmed it was rooted.
I already had CWM downloaded on the tablet (I've used it for a year or two successfully with my phones) and decided to make a nandroid backup. However, when I attempted to boot into CWM recovery, the tablet booted instead into TWRP's screen (w/ RCK, restart, and ADB options). I assume that the root method I used automatically installed TWRP onto the tablet it was somehow "overriding" CWM. When I researched a bit, it appeared as if most people recommend TWRP anyway, and so I decided to uninstall CWM.
After deciding to get rid of CWM, I did it as one uninstalls normal apps. By simply going to the app in my app drawer and dragging it to the uninstall icon. From this point on, I can no longer get past the ASUS splash screen. Power and power+volume down reboots device and gets stuck at ASUS splash screen. Power+volume up does bring me to APX mode, but I never created a NVFlash backup (I had never even heard of it since it appears to be a way to potentially unbrick a device that was bricked by the JB update...but my update went fine).
This sure seems like a brick 2 as per diamondback's thread (http://forum.xda-developers.com/showthread.php?t=1514088), although it is a bit different. I'm stuck at an ASUS splash screen, not an EeePad splash screen. Also, I do not get an "unrecoverable bootloader error" (or any errors, for that matter).
I'm assuming that I'm hosed and will need to pay ASUS to replace the board, but figured I'd at least ask. Any ideas? Thanks!
Any suggestions? Thanks again!
It is no use as ASUS will not do any repairs. I just hate the products sold by this company. Wow what a way to make money thereby troubling its customers. I would rather say dump this company and buy either Samsung or Apple product you will have a company backing you up in case their devices have flaw and will take care of their customers. I am in the same boat and Asus refuses to repair since the bootloader is unlock, and will only repair if Paid $300 and above to replace the motherboard.
Scarilan said:
Asus repair the device. I have sent only the tablet (no the dock) and I have received it after one week. I don't know why but Asus joined with the device a micro-usb card of 16go (that was not my card of 32go, removed before sent my tablet). I won 16go with this story (i take care about virus, don't worry for that )
Click to expand...
Click to collapse
What was on the sd card that ASUS left in your tablet ????
Hi all.
I just bought my (Verizon) Samsung Galaxy S4 Mini, so of COURSE I'm going to root the daylights out of it. That part is done. Not only that, it's setup and running as I wanted with one exception: no CWM recovery.
This is the part where now my phone won't even power on. Here's what I did:
(1) I thought "I reeeally want CWM recovery".
(2) I went here and downloaded the touch version of CWM recovery ... labled Samsung Galaxy S4 (Verizon) ...
http://www.clockworkmod.com/rommanager
(3) Not knowing how to install the .img file, I made an attempt to learn how via the following page:
http://answers.yahoo.com/question/index?qid=20130925031702AAqdm7f
after renaming the .img file to simply "recovery.img" and putting in the SD card root, I read on ...
The page reads
Answerer #1 answered 3 months ago
You need to use Terminal emulator.
Instructions:
1. Put it on the root of the internal sdcard
2. Open Terminal App
3. Run :
Code:
su
Then
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
4. Reboot and now it would work !
Source(s):
Knowledge
... and now I'm stuck.
My phone refuses to power on. Am I legitimately bricked? Is it over? Is it dead?
I sure hope there's a way to fix this. Can someone please help? I'm good with instructions and willing to Odin if need be.
Model = SCH-l435
I'm 99% sure u just nuked a partition on your phone. While on s4 verizon, that mmcblk0p6 is really a correct recovery partition, on your s4 mini it might just be other partition, system, data or kernel partition. Dd is really a dangerous command to be use, moreover when u don't know what you're doing.
Since u mentioning Odin, did u already tried to flash stock rom with Odin?
And what does "and now i'm stuck" means? Not turning on? Stucked at kernel logo? Stucked at bootanimation?
Softbrick usually easy to recover, just flash stock rom with Odin and phone should be booting again afterward.
Sent from your phone
By "stuck", I mean it's behaving like a hard brick. Nothing happens when I attempt to boot it. There's no logo ... nothing. The phone simply doesn't respond to power buttons at all. Now, I'm on a Mac - and - maaaybe the phone can be accessed via usb? When I plugged it into my wife's PC, the pc did respond with the installation of *some sort of* driver.
Is that a good sign?
I've got both a Mac and a PC at my disposal. Would you be game to throw me links/processes so that I might attempt to see if repair is even possible?
Otherwise, I'll be going into a repair shop as I paid for this phone in full not a week ago.
I really, REALLY both appreciate and need help in diagnosing what must happen to get 'er back up and running.
Fixed!
My S4 Mini was the first that they've worked on. All is well. She was hard bricked, for sure.
Go here. They were well worth it: http://mobiletechvideos.mybigcommerce.com/
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Ok, let me rephrase simply.
Can someone with a working Hipstreet Titan, rooted or not, please send me, or post a link to their ROM?
Click to expand...
Click to collapse
I know people have this device, and it's quite reasonable to assume that not all of them are bricked, therefore this request is technically feasible. Further, with a number of people posting about this device in technical forums, I know people with technical knowledge own this device.
I would really hate to throw out an otherwise perfectly good tablet.
Jarod997 said:
I would really hate to throw out an otherwise perfectly good tablet.
Click to expand...
Click to collapse
Hi - did you ever resolve this issue?
beach9000 said:
Hi - did you ever resolve this issue?
Click to expand...
Click to collapse
Not yet. I had given up for a while. Most of my internet searches kept coming back to the same few articles on this website.
I have a lead on someone who has another Titan, but they live seven hours away - it's been difficult coordinating a meeting.
Jarod997 said:
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Click to expand...
Click to collapse
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: http://www.androidtablets.net/forum...eet-titan-a13-7-inch-tab-firmware-needed.html was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
es0tericcha0s said:
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: (link manually removed) was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
Click to expand...
Click to collapse
Thanks for the help! I'll have a look at some of those. I'd really like to have a tablet back that doesn't have a 3.5" screen.
So I managed to get LiveSuit 1.11 installed on Win 8-64, yes it IS doable. But, my problem is I can't get the tablet recognized. The Power+Vol boot takes it in to "recovery" mode, (so reports "adb devices") - does this keep it from being able to be used by LiveSuit?
"adb wait-for-device" hangs
In my Device Manager I have Android Device->Android ADB Interface, and Universal Serial Bus controllers->USB Device(VID_1f3a_PID_efe8) with a yellow exclamation.
I know I had "adb wait-for-device" passing fine at one point, but I don't remember what I had to do to get there. So much trouble for a free tablet.
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
cmstlist said:
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
Click to expand...
Click to collapse
So I managed to get a system backup off of my father-in-law's Titan - just have to figure out how to get it on my brick. I'm having great difficulty trying to do a restore while in recovery mode.
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
adb backup
Jarod997 said:
adb backup
Click to expand...
Click to collapse
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
cmstlist said:
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Aw crap, really? The cutting board a-la-iPad commercial is sounding like such a good idea at the moment.
On the good tablet I could get in the shell - "adb shell", and then "su", but then what? How do you copy all the files off the system through the USB onto the computer from the shell? For whatever reason (and I dislike ADB for this) I could not do "adb pull /* /destination-folder/*" - it kept saying that it was skipping a lot of files. Or otherwise if I was trying other variations on commands and parameters, adb would just spew its help page - never mind telling me what's wrong with the command I just entered.
Why, oh why, is it so hard to take a copy of a good working OS and put it on to another tablet?
But, make you a deal - help me get a good system image off this working tablet and I'll toss it to ya.
If you can find the right mount points on the partition table got may be able to make a system dump using dd. But restoring it I have no idea since there's no custom recovery available for this tablet.
Sent from my Nexus 7 using Tapatalk
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
It works on my TF103CX too. (it is same hardware).
When i bricked my TF103CX, i had around 80% of battery, but i was not able to charge,
so be careful when bricking. Always do interventions to system with full battery.
//I think, we need add our TF103C to xda device list. it will be nice.
I heared that using Intel Manufacting Tool we can get UEFI instead of Droidboot, and boot Ubuntu/Windows on IntelBay tablets. I found guide for Teclast: http://forum.xda-developers.com/android/general/teclast-x98-air-3g-tablet-9-7-2048x1536-t2913035 But i cannot find any UEFI fot TF103C. I dont want to full brick m device with trying flash it.
Here is original thread in russian language.
Thanks
Thanks for helping me rescue my tablet. Much appreciated
Could anyone please confirm if the rooting method may be used on the TF103CG (K018) model? Or in general is the app able to root any device that is anyhow Zen-related?
this don´t work if you have lillipop on tf103c, the droidboot don´t load, You only get Fasboot starting and nothing more...
i want the raw lollipop image ( system.img ) for tf103c
will this essentially work as a factory reset? mine touch isn't working; and i just want to nuke all my data off the device
Hello all, I just ordered a TF0310C (Best Buy exclusive) from woot.com which will be here tomorrow and the closest thing I can find information on is the TF103C (both are Intel processors), and just trying to find as much info on it as I can. I was unable to find any roms or anything for the TF0310c, will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Unbrick not working on tf103c running KK. It looked like it was doing something, but no luck. Any common troubleshooting tips?
m374llic4 said:
Will things from the TF103C work on the TF0310C such as rooting or custom recovery at least?
http://computers.woot.com/offers/asus-transformer-pad-10-1-android-tablet-1
Click to expand...
Click to collapse
I know its a bit late, but perhaps better than never. I'd say those devices are identical, but somehow there is a weird naming mixup. Here are the official ASUS pages for them:
http://www.asus.com/supportonly/ASUS Transformer Pad TF0310C/HelpDesk/
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF103C/specifications/
Whatever you do on the first link, it will be eventually redirected to somewhere that belongs to the second. Their specifications are also basically the same. This is still a guessing game tough, so the best would be to compare 2 build properties, partition tables etc. of those devices to know more.
Rooting will most likely work, Zenroot should do it regardless of device type.
hello,
i have tried different way to unbrick my tf103c, but none is working
i have access to fastboot
i successfully run your bat file to copy the image, but after it reboot and stays on the "asus" logo
if i launch the command after modified the name of the "AS-TF103C-v67.43-capsule.bin" into "capsule.bin", it reboot then a blue progress bar is showing, when the bar is complete the tab reboots, but again it stays on the "asus" logo :'(
do you have any advise ?
Same issue
Hello,
I have the same issue with my tf103c ; i was trying to apply a new update from asus support (to get android 5).
It didn't work and in addition to that, my device results to be bricked.
I have successfully run the bat file, but then i get stuck at Asus logo and device never boot...
Icarolo did you manage to solve your issue ? Is someone really succeed in unbrick tf103c device ?
Thank you in advance
Dead
Hi! I have an asus tf103c and i rooted it with the rootzenfone.apk but now it doesn't turn on at all. after i pressed okay, waited about 15 sec and then i restarted it, but it just turned off. And now it's dead. What should i do?
ASUS K010 (TF103C). I forgot how to enter Recovery
Hello everyone, I have an ASUS K010 (TF103C). The complete model is TF103C-MB1-BLK-DK.
I forgot how to enter Recovery. My Asus is bricked. I know it is possible to enter the recovery because a few months ago I entered and also enter droidboot mode. On that occasion I discovered pressing the buttons energy, volume +, volume - somehow, because I did not work the methods that were in different sites websites, but now I do not remember the exact way of pressing the buttons. I tried many methods but they do not work, only the "Asus looking for incredible" logo appears. The battery has a charge (I charge it manually).
If someone has this same model and knows how to enter the recovery would greatly appreciate it.:good:
I think you can enter the droidboot menu by pressing Volume Up + Power for several secondes.
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
i dont have acces to DROIDboot.
How can unbrick my tf103c.. thanks
Brick3d said:
Welcome to the comprehensive guide on rooting and unbricking your precious TF103C!
Some words of wisdom and truth
You will most likely be here because, you know, your device is bricked.
First of all, I would like to say that none of the downloadable links are made by me. I happened to find them laying around XDA after looking for a solution for a long time.
Skip this if you don't want to know the reason behind this thread
I got this device a while back (my guess is 4 months), and loved it from the start. Rooted it, of course, and soon after, it didn't want to boot anymore.
As there isn't much development going on (due to the locked bootloader), it's hard to find a solution for bricking. While scrolling, I came upon a post from member gouster3, which came to the solution below. I myself have used this successfully, and have my tablet back. In my opinion, also on rooting, there was no dedicated thread available that really explained the steps to root the device, so as a thank you to the guys who got my tablet fixed, here it is!
The rooting process
The rooting of this tablet is quite easy, really! I'll explain in a few simple steps.
Head into settings > security > then turn on unknown sources
Download the Rootzenfone .apk file. get it here
Install the app (if it is still in your notification bar you can just press the downloaded file, or you can navigate to it's location to install from there)
Turn on airplane mode before you open the app
Open the app, and hit "OK, I know, please root!" (when you press this, a number of screens and a popup will show, ignore those)
5 seconds after pressing, restart your tablet.
Hooray! You are now rooted!
Unbricking your device
Luckily, unbricking is almost as easy as rooting the phone, if you know the steps you have to follow. Here's what you could do (it worked for me) if you still have acces to DROIDboot.
As always, install the adb drivers first! get it here
# You can also make sure the correct driver is installed when plugging in the device in DROIDboot mode. In you device manager it should show up as Android Debug Bridge#
Download these files, containing a clean system. get it here
Make sure the device is turned off, and the battery is at least 50% (just to ensure a complete flash before your battery runs out)
Hold volume+ and power untill the asus screen pops up, then release the power button.
Plug in the tablet to your pc (usb cable) when DROIDboot has been loaded.
Open the downloaded folder, and find 'update_image.bat'
Right click the .bat file, and choose 'run as administrator'
A CMD screen should open on your PC indicating the flashing status. All you have to do now (assuming that it works as intended) is wait untill the process is completed.
Your tablet will reboot automatically when the process is done.
That's it! the 2 things that keep this tablet alive. I would like to send a thanks to the members who were so kind to help me out on this.
gouster3, for providing the link to the unbrick solution
Eclipse00, for giving the link to the rootzenfone apk
Monki, for giving me a clean system.img and putting effort into getting my tablet running again
To all of you, thanks!
Click to expand...
Click to collapse
Hi, I see that the thread is old, but I need to fix my old pad. I can do all the steps, but the problem is that I can not find a clean system I can install. I will really appreciate if someone could give me a link to one.
Unbricking tf103c
Hello,
Is it possible to unbrick somehow a device like mine. I dont have either bootloader or recovery or anything (I have two same tablets) and I mess one up. After new update touch screen stopped working so I installed something (I dont remember) i installed new recovery and then tried to install new rom...Every time I power it on (doesnt matter standar od with combos it just show asus logo in search of incredible and that's it. I managed if I press both VOL - and VOL + AND PWRBTN I get something in device manager "Unknown USB Device (Device Descriptor Request Failed)"! Is there anything I can do?
Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?
what you see when u run fastboot devices ?
inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...
THATS BAD do u have working adb ?
No i don't...
HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?