Related
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
I just picked up a Yoga 8 today. did some searching around and found this page instructing how to root it. I was hoping to have a bit more control over the process, but i could not find any other information either through google or through xda. (I realize the thread i linked to is not for yoga 8, but several people said it worked, and when i used it, it did indeed root it)
I would like to experiment with what can be done through the xposed framework with this tablet, but before i go anywhere i want a custom recovery on it so i can do a nandroid backup, should something go wrong. I have not been able to find any custom recovery for this device at all. looking through CWM and TWRP's databases of supported devices, I've come up with nothing. any assistance would be appreciated, whether you know of another recovery (or an unofficial CWM/ TWRP) for the yoga 8 or if you have another method of making/ restoring nandroid backups.
Anybody have this tablet? any success getting a custom recovery running on it?
I picked up one yesterday after spending 3/4 of an hour in front of the stores shelf. I just couldn't really decide which tablet to get. The first thing I've done with it was going online to see how to root. I found a thread where someone posted that using the ideatab method would work on the yoga too. But I was too hesitant because I had just updated the firmware. But it would be great if this little thing would get some developer love.
I have installed CM11 on my old razr HD before handing it down to my wife and already thought about installing it on my note 3.
Rooting is done using Framaroot 1.9.1 (old Framaroot had no Barahir exploit). You can make a backup using MTKDroidTools and you can flash using SP Flash Tools. All tools can be found here at xda-developers. Unfortunately I don't know about a recovery for the time being, I'd like that too
Mikegrmn, I found those parts about rooting tool for the ideatab working on the yoga, and I ran them after updating to lenovos latest firmware. I can say it worked perfectly.
AP756, thanks for the info. Still hoping for custom recovery but at least I can try a few things now.
TWRP for 3G version of B6000-H (( not my work )) >>> https://drive.google.com/file/d/0Bzwq8_00PhMUYmg4ZjlldW9SQXM/edit?usp=sharing
Root, lenovo driver's and knowdelege needed
Edit : picture with battery stat's after rooting and some changes in rom. Managed 20 h of screen on time with 50% brightness, wi-fi always ON and still 28% batt left.
criszz said:
TWRP for 3G version of b6000 (( not my work )) >>> https://drive.google.com/file/d/0Bzwq8_00PhMUYmg4ZjlldW9SQXM/edit?usp=sharing
Root, lenovo driver's and knowdelege needed
Edit : picture with battery stat's after rooting and some changes in rom. Managed 20 h of screen on time with 50% brightness, wi-fi always ON and still 28% batt left.
Click to expand...
Click to collapse
unfortunately I have the non-3G version of the yoga 8 (I dont think the 3G version is available where i am).
I'm wary to try it since it's not the exact same device. I would personally wait for more support to be available for custom stuff.
It will work but let me do more research about it
Sent from HTC One 802w Dual Sim with my hand...
this is TWRP for B6000-F WIFI only >>>> https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
criszz said:
this is TWRP for B6000-F WIFI only >>>> https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
Click to expand...
Click to collapse
tried to install it and completely failed the easy way (running the included batch file). the good news is i have a bit of experience in linux so i opened the batch file for reference of commands needed, transfered the files over adb to the tablet, and then did the rest from there using the commands from the batch file with an android terminal emulator and the hackers keyboard (not required by still awesome). i used ROM manager to reboot to recovery and I AM THERE.
Thanks so much for your help. I am also going to, upon your signature's request, use the thanks button.
Thanks, I'm glad to hear you're fine now. Because bat file didn't worked for you makes me think you don't have driver for processor installed.
Trimis de pe al meu Lenovo B6000-H folosind Tapatalk
I've got the drivers installed properly. i used them to root it and to send the recovery over adb. it coughed back that I didn't have the permissions to copy the file (i was running admin cmd) so i set the default action for SuperSU to allow, i tried again, and it still didn't work.
Either way it is done now and working. i did a backup and copied it to my computer, so i can start playing around with it.
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
johnsongrantr said:
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
Click to expand...
Click to collapse
ROM Manager has the ability to reboot to recovery...or if thats the only thing you need to do, download swift reboot
https://play.google.com/store/apps/details?id=com.Jerry.swift_reboot
I was more looking for a button combo, thinking of a solution to maybe overwrite the correct recovery or something of that nature. But thinking about it, there's probably one recovery built into the boot loader and a separate image as just the recovery maybe? The button combo is proabaly just different areas of the bootloader instead of it redirecting to a different image like what happens on other devices. I think I remember the transformer having this "issue" where it seemed to have two. I'm sure someone will come along with a fix this at some point, it functionally works, just not ideal.
I've got the yoga 8 3G/wifi version. Rooted with farmaroot and installed cwm with mtktools. But I need stock recovery back. Can anyone provide with it cus I don't wanna flash stock os n start all over
johnsongrantr said:
I got one of these last week because I was very curious on the MK-8125 (quad a-7)
http://www.kingoapp.com/android-root.htm
worked for rooting
https://drive.google.com/file/d/0Bzwq8_00PhMUTm5uYkdrd19QWE0/edit?usp=sharing
worked for twrp
what I'm still unable to determine is how to actually enter recovery without sending adb reboot recovery, the VOL + power seems to still enter the chineese recovery. But other than that it's fine and functions correctly.
If someone knows how to replace the default recovery with twrp and the button combo that enters that recovery with power off please advise.
I have my eye on this as well
https://github.com/TeamYogaBlade/android_device_lenovo_b8000
Getting in to Recovery is easy.
Hopefully adapting the b8000 build to the b6000 won't be that hard once they get it working.
Thanks guys for the info, things are working great so far
Click to expand...
Click to collapse
Hold Power button + (Vol+ & Vo- together) and hold it few few seconds until you see a black screen where you will see selection between recovery and normal boot. Read the screen. Selection of option using volume up button and entering to selection is vol down button. Once you selected Recovery and pressed vol down, you will see screen with triangle. Now press power button gently. There you go.... You are now in Recovery (either 3e or your custom recovery).
Hope it helps.
goldfinv said:
I've got the yoga 8 3G/wifi version. Rooted with farmaroot and installed cwm with mtktools. But I need stock recovery back. Can anyone provide with it cus I don't wanna flash stock os n start all over
Click to expand...
Click to collapse
hi
which version of cwm did you install ?
and where can i find it ?
thanks
Ricx94 said:
tried to install it and completely failed the easy way (running the included batch file). the good news is i have a bit of experience in linux so i opened the batch file for reference of commands needed, transfered the files over adb to the tablet, and then did the rest from there using the commands from the batch file with an android terminal emulator and the hackers keyboard (not required by still awesome). i used ROM manager to reboot to recovery and I AM THERE.
Thanks so much for your help. I am also going to, upon your signature's request, use the thanks button.
Click to expand...
Click to collapse
hi
batch file didn't work for me too, and unfortunately i have no experience in linux.
so would you be kind to explain to me how you did step by step, please ?
thanks
Tuan79 said:
hi
which version of cwm did you install ?
and where can i find it ?
thanks
Click to expand...
Click to collapse
I used mtkdroid tools to install cwm on it
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Hello there, I have a Multilaser M8 and it has a ROCKCHIP 3066 processor. I've already lost one M8 because of a faulty firmware available on their website. It apparently has no recovery mode as I couldn't manage to get it to boot, the only thing that it shows is the android logo with a exclamation mark. I know that there's a way to get past this window on some devices, but mine doesn't have the + and - volume buttons and I've tried touching the window on the corners and pressing the available buttons with different combinations but none of them worked. I've also spent a lot of time searching for something on Google, but found only frustrated people who where also a victim from that firmware. As my hands itch to change something on my tablet, I had to do something to make it safe as I have no methods of recovering my device if I manage to brick it. So, I managed to dump my rom using the romdump method wich consists in dumping the rom using the terminal emulator. The files that I've got from this dumping are: boot.img, checksum.md5, config.gz, recovery.img, system.info.gz and system.tar. The firmware available on the website is a .img file that must be flashed using RkBatchTool. So, what I want to know Is if with those files I can manage to restore my system so I'll have no worries if I get bootlops while trying to mod my tablet. The first thing that I would like to do is to manually install CWM, but I believe that it's very risky and I must be sure that I'll have a backup from the system to rely on. I'm sorry about my English and thanks in advance!
Update: I've successfully installed CWM on this device and I'm able to use it with my usb keyboard.
bump
how?
Hi!
How you did it?
Olá, como você conseguiu instalar?
Wo11ven said:
Hello there, I have a Multilaser M8 and it has a ROCKCHIP 3066 processor. I've already lost one M8 because of a faulty firmware available on their website. It apparently has no recovery mode as I couldn't manage to get it to boot, the only thing that it shows is the android logo with a exclamation mark. I know that there's a way to get past this window on some devices, but mine doesn't have the + and - volume buttons and I've tried touching the window on the corners and pressing the available buttons with different combinations but none of them worked. I've also spent a lot of time searching for something on Google, but found only frustrated people who where also a victim from that firmware. As my hands itch to change something on my tablet, I had to do something to make it safe as I have no methods of recovering my device if I manage to brick it. So, I managed to dump my rom using the romdump method wich consists in dumping the rom using the terminal emulator. The files that I've got from this dumping are: boot.img, checksum.md5, config.gz, recovery.img, system.info.gz and system.tar. The firmware available on the website is a .img file that must be flashed using RkBatchTool. So, what I want to know Is if with those files I can manage to restore my system so I'll have no worries if I get bootlops while trying to mod my tablet. The first thing that I would like to do is to manually install CWM, but I believe that it's very risky and I must be sure that I'll have a backup from the system to rely on. I'm sorry about my English and thanks in advance!
Update: I've successfully installed CWM on this device and I'm able to use it with my usb keyboard.
Click to expand...
Click to collapse
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?