Hello,
I'm having a problem. I've sold my prime via ebay.
Now, after I wanted to clear everything on it, it seems like I've bricked it.
Everything worked well, until i booted into TWRP and did all the wipes there:
cache
dalvik cache
factory reset
system
internal storage
format data (here i got a warning that all media will be deleted)
After a "successfull" wipe, the devices hangs on the asus boot-logo.
What I've tryed so far:
Boot into TWRP to mount sdcard - not working
Boot into Fastboot - PC not recognising
Install universal nake driver - getting error, that drivers coudn't be installed
When I plug it into my pc, it's getting recognized either as fastboot (when in fastboot mode) or as android device.
Running adb device shows empty list. with adb i mean the adb.exe on pc, since i haven't a so called "adb setup" yet.
When I'm in TWRP and go to reboot->power off I get the message "No OS installed, do you want to power off?"
Is it hard bricked now? Or is there still a solution for me?
ad_on_is said:
Hello,
I'm having a problem. I've sold my prime via ebay.
Now, after I wanted to clear everything on it, it seems like I've bricked it.
Everything worked well, until i booted into TWRP and did all the wipes there:
cache
dalvik cache
factory reset
system
internal storage
format data (here i got a warning that all media will be deleted)
After a "successfull" wipe, the devices hangs on the asus boot-logo.
What I've tryed so far:
Boot into TWRP to mount sdcard - not working
Boot into Fastboot - PC not recognising
Install universal nake driver - getting error, that drivers coudn't be installed
When I plug it into my pc, it's getting recognized either as fastboot (when in fastboot mode) or as android device.
Running adb device shows empty list. with adb i mean the adb.exe on pc, since i haven't a so called "adb setup" yet.
When I'm in TWRP and go to reboot->power off I get the message "No OS installed, do you want to power off?"
Is it hard bricked now? Or is there still a solution for me?
Click to expand...
Click to collapse
You have wiped system so that's why you cannot get into it. Practicly you have deleted all data on your device.
Go into TWRP and then connect to PC and adb push there any ROM compatibile with your bootloader.
Sent from my Transformer Prime TF201 using Tapatalk HD
qery said:
You have wiped system so that's why you cannot get into it. Practicly you have deleted all data on your device.
Go into TWRP and then connect to PC and adb push there any ROM compatibile with your bootloader.
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Huuuh, that's good news. But how can I get into adb, when I connect it to the PC adb can't find any devices.
What version of TWRP you have?
qery said:
What version of TWRP you have?
Click to expand...
Click to collapse
Probably one that doesnt see microsd. Otherwise the solution would be to simply install a rom from there.
whycali said:
Probably one that doesnt see microsd. Otherwise the solution would be to simply install a rom from there.
Click to expand...
Click to collapse
that's what I wanted to try next... buying microsdcard and try it from there.
ad_on_is said:
that's what I wanted to try next... buying microsdcard and try it from there.
Click to expand...
Click to collapse
you dont have one in a phone or something? no matter you can get a small one for a few dollars. It really only needs to be 500 mb.
SOLVED
yeah... solved it! put a rom onto an external sdcard and installed it via twrp.
whycali said:
you dont have one in a phone or something? no matter you can get a small one for a few dollars. It really only needs to be 500 mb.
Click to expand...
Click to collapse
no, I never needed one untill now
Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Flash stock rom
Guide on how to do that + download stock rom from here - click here
You should be fine after flashing stock rom. :highfive:
hard bricked I guess
You should be fine after flashing stock rom. :highfive:[/QUOTE]
First of all, thank you for replying to thread, I appreciate it. This procedure seems really great but like I can't have the RCK menu and that my computer only recognize my devise through apx mode, it doesn't work. Well it looks like I m in a no win senario on this one. I guess I'll send it back to Asus for a software repair. Even though I unlocked it, I think I found a work around so it won't cost much, and since (from what I've heard) I l'm in Europe I have better chances to have it repaired for almost nothing.
TF300T almost bricked
khajj16 said:
Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Click to expand...
Click to collapse
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
Hi aldossir! Thank you for answering . Like you have been in the same situation I will follow your instructions to the letter.
1) I do have the SDK tools, fastboot and adb as well
2) My computer doesn't recognize the device when under the bad CWM. I have the drivers but I guess they aren't the correct ones. So, if you don't mind I'll ask you for instructions and for a link toward the correct ones so I can install them.
For steps 3 to 6, I'll see about that once I get my device recognized.
Note: I will use windows vista to do this. However, if you advices me that it is preferable to use Windows 7, I'll do it.
In the meantime, I will recharge my tablet.
Thank you again.
khajj16 said:
Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Click to expand...
Click to collapse
I dont know if it is your case or not... but I beleave was in your same condition, the only recovery able to read and write our device memory is the last twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) on my device with the same problem I was able to restore the system from the backup...
now you have an other problem... if you dont have any backup to restore i dont know what you can do, the recovery work fine but i wasn't able to install any CM10.1 but i'm confident you can install a stock version....
I hope my suggestion can help you, good luck and of coure all the procedure are at your risk
lk2l said:
I dont know if it is your case or not... but I beleave was in your same condition, the only recovery able to read and write our device memory is the last twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) on my device with the same problem I was able to restore the system from the backup...
now you have an other problem... if you dont have any backup to restore i dont know what you can do, the recovery work fine but i wasn't able to install any CM10.1 but i'm confident you can install a stock version....
I hope my suggestion can help you, good luck and of coure all the procedure are at your risk
Click to expand...
Click to collapse
Well I'll try but without the correct fastboot or adb drivers, it's going to be difficult. But it's worth a try. And about the "of course the procedure at your risk", I guess it can't get any worse, can it? ^^
Anyway ty
...mmm maybe my reply was not the clear, you are right...
I dont think it can be wrost, I'm sure this must not be done if you have ICS (4.0)...
I update my tf300t to JB 4.2.1 and after that I unlock the bootloader with the asus tool (from asus site), and installed the CWM 6.0.2.3 using fastboot, at this point the tablet work correctly but recovery was unable to read the sd card (internal and external). I tried to install other version of cwm and TWRP recovery, at the end found the TWRP dedicate for who has done the update to 4.2.1, installed and after done the backup, I try to install CM10.1 and all the system was not able to boot over at the asus screen, fortunatly the backup works fine I restored it and now it's back to normal (+ root lol)
I think the 4.2 bootloader need some specific rom... in any case for the moment it's fine.
now I will explain better witch procedure I followed
1) to have the correct driver for fastboot you can install asus PC sync from the asus website
2)download fastboot from internet and extract to c:\fastboot\
3)download from goo.im openrecovery-twrp-2.4.4.0-tf300t-4.2.blob and put in the fastboot directory
4)boot the tf300t holding power + volume down and connect at the pc
5)open command prompt (run cmd.exe) and navigate to c:\fastboot\
6) to know if the device is connected correctly use the command "fastboot devices" it should show you a string with numbers and letters
7)to install the recovery use the command fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
8)Reboot with the command fastboot -i 0x0B05 reboot-bootloader
Now you have the TWRP 4.2.2.0 specific for the bootloader 4.2 with this you can install rom and try to restore the system, in case if you dont find any other solution i can try to share my system back-up. but I can't garanty it will work at 100% (maybe 98% )
I hope I was more cleare than before lol
let me know if it works for you.
sorry if I didn't put direct link but this is my second post and I cant insert any link until post n°10...
TF300TL software brick solved!
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
You saved my device health, the steps you describe worked flawlessly for my ASUS Tranformer pad TF300TL (4G) LTE software brick, thank you very much!!! :laugh: :good: I am a new user and I want to bring my knowledge to the next level with XDA
i have similar situation
i have similar situation with my tf300t but i can't connect to fastboot tool. my device is stock to asus logo and i just can connect to apx mode please help
This should fix it
Link to my thread--> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps!
I can't connect to fastboot mode. Any help about that?
Sent from my GT-N7100 using xda app-developers app
Fixed my problem and got my RCK back
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
The above works to get RCK back. Perfect many thanks.
I can still boot to CWM recovery. When I connect it to my PC, HTC sync starts and acts like it's going to connect, but then doesn't. It doesn't show up in My Computer, but it would appear the driver is installed correctly.
On my Mac, again HTC sync manager starts and it acts like it's going to do something but does nothing.
If I put it in sideload mode, adb tells me there are no connected devices. I am super scared I bricked my phone
All the stuff I'm finding with google and xda forum searches are coming up only with solutions that require me to be able to copy files to the device. That's exactly what I can't do.
jerkmenistan said:
All the stuff I'm finding with google and xda forum searches are coming up only with solutions that require me to be able to copy files to the device. That's exactly what I can't do.
Click to expand...
Click to collapse
start at post #26 here -->> http://forum.xda-developers.com/showthread.php?t=2301470&page=3
Your fine be patient
clsA said:
start at post #26 here -->> http://forum.xda-developers.com/showthread.php?t=2301470&page=3
Your fine be patient
Click to expand...
Click to collapse
Thank you for your reply, however I am not able to do that. ./adb devices -l says I don't have any attached devices. When I try to run ./adb push arhd.zip /data/media I get "error: device not found". This is from fastboot USB and from CWM.
edit: I just tried to do the sideload thing again, and that worked. So, for the record, go into fastboot USB and run ./fastboot erase cache then boot into CWM and install from sideload.
I had a similar thing happen to me. Just did something without paying attention and boom I wiped the entire phone in recovery. The only fix I found that worked was ordering a USB OTG cable from Amazon (it was only like $5 w/ shipping) and using that to push files to the phone. Or try running the RUU. I heard that worked for some. But it happened to me before it was released and in on Windows 8 so even after it's release I couldn't run it on my laptop
Sent from my HTC One using xda premium
Hi I have moto G 2015 osprey XT1541, its unlocked running cyanogenmod
I recently upgraded to CM 14 experienced problems instantly, all the google apps wpuld crash.
Reverted back to CM 12 which worked and it had an error whilst upgrading in recovery,
something like
E:Failed to map file
E:Error exit from the fuse process :0
Installation Failed Installation Aborted
I have tried multiple roms, all come back with same error message. The recovery on the phone is the cyanogenmod one. Also in recovery if I do system reset I get
E: Failed to mount /data (permission denied)
I am having to try installing roms via sdcard as the phone is not recognised by my computer.
Any Ideas?
I would format userdata in bootloader then install TWRP and use that to install the next rom.
es0tericcha0s said:
I would format userdata in bootloader then install TWRP and use that to install the next rom.
Click to expand...
Click to collapse
How do I format userdata? I dont have that option in the bootloader. When I try to install anything using cyanogemod recovery including TWRP I get the same error message.
fastboot format userdata
fastboot format cache
If that doesn't work then you'll want to go back to complete stock with the original firmware for your variant (and carrier if yours came from one originally).
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
AndyGLowe said:
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
Click to expand...
Click to collapse
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
es0tericcha0s said:
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
Click to expand...
Click to collapse
I doesn't even show in Device Manager, I have tried another system with Win 7 on and that comes up with a notification saying a unrecognised device has been attached. But it doesn't make a difference if you install the drivers or look in device manager, had exclamation mark next to device but you cant do anything. I also have Ubuntu dual loaded on this system and that doesn't recognise it either.
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
sahil soni said:
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
Click to expand...
Click to collapse
did you guys solve your problem I have the same exact issues?