OK I have a transformer prime that I cannot read with adb because the driver won't install. I have win 7 x64 and in the device manager it shows transformer and driver not installed. I rooted and unlocked my prime and when I tried flashing a rom I put the zip file in the external sd card so I go ahead and boot into recovery CMR 5834 and wipe everything and when I go to look for the zip file I can't find it because I can't access the external only the internal now I am stuck! I need some help if anyone can point me in the right direction or is this prime bricked? no nandroid. and can't read prime in adb it keeps telling me "no device found"
you have to get the naked drivers in android development
NandoLM said:
OK I have a transformer prime that I cannot read with adb because the driver won't install. I have win 7 x64 and in the device manager it shows transformer and driver not installed. I rooted and unlocked my prime and when I tried flashing a rom I put the zip file in the external sd card so I go ahead and boot into recovery CMR 5834 and wipe everything and when I go to look for the zip file I can't find it because I can't access the external only the internal now I am stuck! I need some help if anyone can point me in the right direction or is this prime bricked? no nandroid. and can't read prime in adb it keeps telling me "no device found"
Click to expand...
Click to collapse
Can you boot into Recovery? It sounds like it. If so, adb devices doesn't return anything?
If it does, the adb push (zip) /sdcard/(zip) works fine. It just takes a while to push the file over adb. or you can do adb push (zip) /data/media/ (zip) and it will go to the internal SD as well.
Related
Hi, I'm looking for original recovery image for folio so i can return my folio for warranty repair due to the "damaged internal storage" and SD card not detected problem. Other people have that problem but no one got a solution.
There was only one link from dexter
but it does not work for me (maybe due to sd card not correctly detected? sd card can be detected for some other mod though). Also when i open the zip file i notice the files types and location in the "folio stock image" is different from the mod that works on my folio.
Someone seems to have a Folio Original Recovery(apply via recovery).....how to do that actually?
Can it be fixed by fastboot (never done this and not sure what it is about actually) as done here http://forum.xda-developers.com/showthread.php?t=1012980#12482544
http://bb2k.org/folio100wiki/index.php/FolioMod_Issues#Internal_storage_give_problems_.2F_no_enough_space_.2F_internal_storage_results_damaged
If you have sd damage or something like that it must be the mbr .At the end of lost partition method 2 , use this file mbr.mbr inside zip http://www.box.net/shared/suinl2fzqb63jkqaispj with adb
Hope this can help you but you need to install sdk and adb shell on you computer with the correct folio driver to connect your tablet in fastboot
Warning if you re not sure of what you do you should not do this but if it "bricked" it Will not be worst
if you are with Windows seven sometimes it s hard to install proper driver for folio try to use pdanet to do that if you still have waiting for device in adb shell
I recently seemed like a brick on my transformer prime. I tried flashing EOS rom and the system just froze on eepad screen. I still had access to Fastboot and Wipe data but no recovery whatsoever. I figured out i was missing the blobfile which got me back to cwm 5.8.2.0 and i transfered a stock rooted rom to the sd card to reflash but it wouldn't read my sd card, i tried 3 different ones. It just seem like its not finding a sdcard drive on the device. I tried adb pushing the files to internal sd but when im in recovery, my computer recognizes the adb device but the adb in cmd keep saying adb device not found. Any ideas? i been searching on the forums for the past 2 weeks to find a solution but no luck
j8dailo said:
I recently seemed like a brick on my transformer prime. I tried flashing EOS rom and the system just froze on eepad screen. I still had access to Fastboot and Wipe data but no recovery whatsoever. I figured out i was missing the blobfile which got me back to cwm 5.8.2.0 and i transfered a stock rooted rom to the sd card to reflash but it wouldn't read my sd card, i tried 3 different ones. It just seem like its not finding a sdcard drive on the device. I tried adb pushing the files to internal sd but when im in recovery, my computer recognizes the adb device but the adb in cmd keep saying adb device not found. Any ideas? i been searching on the forums for the past 2 weeks to find a solution but no luck
Click to expand...
Click to collapse
CWM does not have access to external SD cards on the Prime. No way around it.
how would i go about pushing rom files to update it without the ability to read sd or mount internal sd? my computer reconigzes the android ADB devices when i boot into CMW but when i use adb to push files over it keep saying device not found
My transformer prime has been rooted and unlocked and im using TWRP recovery. After plugging it into the computer and using Android File Transfer to put a rom on the sd card, after flashing it the prime wouldn't let me copy things into internal storage or delete things off of internal storage! So i decided to try the wipe of internal storage and it is now only booting into the splash screen.
PLEASE HELP PLEASE!!! ANYONE!!
-thanks
Do you have access to adb or fastboot? Have you used adb or fastboot before? If you have access to adb or fastboot then you're still okay. The dev section has a lot of detailed posts in regards to pushing files to your tfp via adb or flashing a rom through fastboot.
I had a similar problem, and fixed it. It's seemed to have helped others. Try this.
I inherited a T959 that I cant get to unbrick. It boots to splash ("Overstock", whatever that is...) and hangs. I can get to recovery (CWM 2.5.1.3 w/ voodoo lagfix) and I can get it into download mode from there. I cant get ADB to find device, I cant get it to show up on ODIN (3 v1.0 or v1.7), and I cant see sdcard in CWM recovery. Any ideas?
Setup:
Windows 7x64
Latest USB drivers.
What drivers do you have installed? Have you tried a different cable?
Funny thing, I read a few posts about bad USB cables but thought "naw, that can't be it". Turns out it is.
I still cant get the SD card to read from CWM, but I will ODIN it back to factory and see what I can do. Thanks.
You can mount the internal or external sd card trough cwm and coppy your files, or what ever rom you wanna flash, you just gotta have the right drivers and then go into (mounf and storage) then mount your sd card or internal storage...
Got it all up and running. Thanks.
I may have messed up the flash steps when I was trying to flash SuperNexus from Froyo? So I did the following first:
Make a Nandroid backup
Then I put those two files on the phone with the following adb commands:
adb push SuperNexus-2.0-vibrantmtd-BUILD4-update2.zip /sdcard/
adb push gapps-jb-20130301-signed.zip /sdcard/
After that I did
Do a Wipe/Factory Reset
Now I'm lost at the following step:
Flash SuperNexus ROM
On the CWM recovery interface, now when I select
install zip from sdcard
and then
choose zip from sdcard
I can't find the sdcard directory from the long list of directories such as Android, DCIM, data, external_sd, voodo, etc.! Where is sdcard?
Is it because the Nandroid backup didn't back up those two files (SuperNexus and gapps) because I did them backwards?
Now the screen only shows an open trash can with the Android logo, and it does not response? Is the phone bricked??? What can I do now?
Someone, please help!
When you click choose zip from sd card that takes you to your sd card and every folder contained in it. I usually just download ROMS with my phone and it puts them in the download folder. So when I "choose zip from sd card", then everything is in the folder "download". Next time either download with your phone or connect to your pc and put the files in a folder you will remember, example : sdcard/download. If you have pushed with adb then it might not be in a folder at all, I'm really not familiar with adb, maybe they were put in a folder named adb? I'm not familiar with the screen you speak of either, but it sounds like you have soft bricked your phone. Go back to stock with this guide http://rootzwiki.com/topic/605-guid...nja-apps-everything/page__p__11106#entry11106 if you are indeed soft bricked.
Sent from my SGH-T959 using Tapatalk 2
mj56gt said:
I may have messed up the flash steps when I was trying to flash SuperNexus from Froyo? So I did the following first:
Then I put those two files on the phone with the following adb commands:
adb push SuperNexus-2.0-vibrantmtd-BUILD4-update2.zip /sdcard/
adb push gapps-jb-20130301-signed.zip /sdcard/
Click to expand...
Click to collapse
Just plug in you usb select mass storage and copy it in the main memory(where Android, DCIM, data, external_sd, voodo exist ) not in the External memory.... the other procedure rather than adb pushing was correct... this will be fine.:good:. try again and let us know if you passed well..... for being more sure put out your mini sd card from phone.....
mistermish2000 said:
Just plug in you usb select mass storage and copy it in the main memory(where Android, DCIM, data, external_sd, voodo exist ) not in the External memory.... the other procedure rather than adb pushing was correct... this will be fine.:good:. try again and let us know if you passed well..... for being more sure put out your mini sd card from phone.....
Click to expand...
Click to collapse
Thank both of you for the kind suggestions!
It was quite scary for me since this was the first time I encountered such a scenario. After the soft brick, I managed to boot the phone into download mode many times, but the computer would not be able to detect the phone! Then accidentally I booted it into recovery mode, and the computer somehow recognized it. So I decided to just push the .zip files again with adb, After that everything went smoothly.
Now I'm fully enjoying JB!
glad you figured it out somehow... get used to it it will become easy to you when you do this again and again cause this phone can't be brick-able.. :highfive: