Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
Related
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
fizzle101 said:
Hi all
I have a problem with my hero not being recognized by my PC. This happened after a weekend trip and i charged the phone with iphone USB adapter as i lost my one and now after returning from my trip i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message.
Also my Amon_Ra recovery i used has been wiped and i cant get into recovery or install any rom at all.
I am thinking this might be the same USB brick that affected some Desire owners but i am not sure.
So please if anyone can help me, please do.
Thanks in advance.
Click to expand...
Click to collapse
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Can you try booting in fastboot and tell me if that is recognized?
it still doesnt recognize it in fastboot
fc_Kuro said:
this happen to me. What i did was switch my phone off, plug in the usb and switched it back on. then wait for windows to say it not recognised. then go to to device and printers and uninstall the drivers for the phone. Disconnect and reconnect the usb back to the phone and it it will pick it up.
Click to expand...
Click to collapse
i have tried that and it doesnt help
fizzle101 said:
i connect my hero to my PC to be greeted with the "USB Device Not Recognized" message
Click to expand...
Click to collapse
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
ok i will give that a try
crk23 said:
I hav the same problem. In recover mode it works but then turn on the phone, there is no popup options as before. Tried around with drivers but didnt work either. But found a solution which is very convenient. I dont know if it works on other ROM versions but I'm on 2.1 (Villain10).
- Install extended control widget (dont remember where I got it but you can google, it seems I cannot find it on the market)
- Add this widget to the home screen: Menu/Add to Home/Widget/ Extended Control bar (you can choose the size from 1x1 to 1x4) then select "Mass storage" at the bottom, apply.
Now you have a widget to turn on/off USB storage. When you connect Hero to the PC, just click on this widget then the PC will connect to the SD card, and click one more to turn it off.
Click to expand...
Click to collapse
that didnt work. o well i guess i am stock with the rom i have there.
fizzle101 said:
that didnt work. o well i guess i am stock with the rom i have there.
Click to expand...
Click to collapse
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
robocik said:
i've got this problem once and it was as simple as the cable was damaged...
i changed the cable and since then, everything works try that.
Click to expand...
Click to collapse
i have tried everything. changed the cable, used different pc but nothing works. i think is a hardware problem, something might be broken inside or something like that
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
baklap said:
Did you ever got this solved? I have the same problem only i use stock rom 2.1 Hero.. driving me nuts ...
Click to expand...
Click to collapse
No i havent and i gave up trying because i dnt think there is a fix for it. if yours is unrooted and the warranty is still valid you should consider returning it to HTC maybe they might replace it
got the same problem. Any solution so far ??
ddotpatel said:
Sounds like its just a driver issue. Have you tried plugging it in, when you get that message open DEVICE MANAGER,... Find the yellow "!", right click it, uninstall, unplug phone, reboot PC.
.... Then use BTDAG's [Guide] How to Setup Correct Hero Drivers (for x86 & x64 users)
Click to expand...
Click to collapse
Did you try that?..... You need to do the reboot PC/Laptop after uninstalling ALL HTC drivers! Then when you reboot PC, plug phone back in, should say "not recognised" again,... then follow BTDAG's guide. T'is definitely a driver issue!
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
You need to use....
fastboot devices
....when your are in fastboot.
What happens when you go into your recovery, select "Toggle MS/USB" with USB connected to PC?
okay
fastboot devices command shows some serial number.
then i tried adb remount, it gave an error....
enabling usb-ms with cable attached gives no response
ok i think it might be USB driver like ddotpatel said but i am not sure.
i reinstalled my whole windows 7 to 32bit now instead of the 64bit version i was using before and today i just connected my hero to my PC and windows 7 did its thing and installed the drivers and finally my hero can mount the SD card in my PC again although i kept getting this can perform faster in USB 2.0 port or something like that i didn’t care as long as i can mount my SD card again.
now went into fastboot and used the fastboot device command and i could see my hero serial no. but when i try to flash the amonra recovery i got the permission error (i cant really remember). i tried flashing using the adb method but still no luck.
so i went to market and downloaded rom manager and used it to flash clockwork recovery and now i could boot to clockwork recovery.
from this recovery i can now flash any rom i want and although there are still a few more problems i am glad now that i can flash custom roms again.
the problem i can see so far but i can deal with is
1. i don’t think fastboot commands work even if the phone is detected.
2. SD card mounts at USB 1.1 speed. (i have tried different ports and cable but still the same thing and this is the ports i use for my N1, Desire and my other android phones with USB 2.0 speed)
PS: adb commands for pushing and removing apps is working.
Hope this can be helpful to those experiencing the same problem.
Instead of re-installing your entire OS just use usbdeview to remove the failing drivers.
Also remove any old HTC Sync installs and install the latest version.
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply
Hi guys!
I have tried to get Android onto my phone and I'm stuck. I'm using the files/instructions from this thread. (HSPL has been done and confirmed)
I noticed there's a similar thread, but they seem to be talking about a different problem, even though it happened at the same step.
Looking at the step-by-step list from that thread, I am stuck between step 10, step 11 and step 12:
- I successfully flashed RHODIMG.NBH
- Took out the battery, booted up with USB and there's the blue screen of the miniPoopLoader (tee-hee, it says poop ).
- Text scrolls by, ends with -- suspend --.
That's it, nothing happens. I can reboot, and it just goes there again. One of the snippets of text reads "flash_read_image: failed 0 errors"
I thought this might be all fine afterall and that I just had to use Fastboot erase blabla to go ahead. But obviously that doesn't work. Most likely because step 12 says install drivers, but no request to install any drivers comes up on my Windows (using Win 7 64 - also, drivers in the package are all Vista - will those work?), which I assume is either because the phone never boots up "far enough" for windows to detect the device, OR because I'm a retard to all major phone hackers here, because I just have to copy them somewhere. (didn't find anything on the boards to suggest the later is true, but then again, who knows).
So, where's the stupid newbie mistake that I overlooked? This isn't the first flash I'm doing, flashed win 6.1/6.5 onto my Touch Pro (1 ), using a fine how-to on this board, and constantly tweaking my S2 and S3, but this seems to be too much for me to figure out.
Thanks for any help!
What phone are you using?
Basic trouble shooting would be.
Task 29, re-download & reinstall minipooploader.
This video gives some idea of what you should expect.Useful info starts around 7:00
http://www.youtube.com/watch?v=_qNCHqGPofI
I have never heard of a suspend error/dialog. Perhaps someone else can chime in.
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
arrrghhh said:
I think he just hasn't prepped for fastboot properly.
Sometimes I have to reboot a few times to get the cable plug timing or *something* right... Not sure what it is, but occasionally when doing a new flash to Android I had issues with fastboot not being recognized - and obviously you won't be able to flash recovery without fastboot being functional.
So before you task29 and reinstall OP - try a few different things - try plugging the cable in BEFORE you boot the phone. Try pulling the battery again, and do the plug in cable before you turn it on. I can't remember what the secret is here, I know for getting into recovery you have to start holding power as soon as you see the blue screen - but obviously this is beyond where you are at.
Click to expand...
Click to collapse
To enter fast boot you need to have the phone totally off (not rebooted) with the usb cable removed. Then plug usb cable into the phone with the phone off. Then press and hold the power button until the blue screen is done. Sadly I have been doing this all morning trying to resolve a problem of my own.
Tried that, resulting in a slightly different screen (see attached image). Other than that, no difference. I still don't get any request for the HTC drivers and going Fastboot erase recovery results in "waiting for device".
Could you check the list at the thread I linked in the original posting and tell me if I somehow missed something?
Step 10 worked fine.
Step 11 I guess is what Wizardknight commented on.
Step 12 is what confuses me and what's possibly the culprit here?
I bet it's just that without the drivers my PC can't send the Fastboot commands to the phone.
Everything before that worked fine with no errors and everything after that, is just hammering away at the console.
Thanks guys!
Sent from my GT-I9300 using xda premium
Urgh, no idea why it uploaded the picture sideways, sorry.
When instead I press the power button as soon as I see blue (as opposed to hold it all the time), I get the following (see image)
Sent from my GT-I9300 using xda premium
Looks like it is working ok on the phone. I am assuming you installed fastboot and ADB on the PC.
What happens when you open a command prompt and type fastboot devices?
BTW here are the more official install directions.
Lists nothing. After hitting enter, I'm back at the \android-sdk\platform-tools promt.
Sent from my GT-I9300 using xda premium
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
wizardknight said:
Was the usb port on the phone working ok in WM? Could you sync and other data related activities?
Does any unknown devices show up in your device manager on the pc?
Have you tried any other usb cables?
Click to expand...
Click to collapse
This might be where you're going to have to go next OP. Sounds like it's all OK - so try different cables, different USB ports on the PC, and if you can - an entirely different PC altogether.
Vortagh said:
Solved.
I tried different ports and a different cable before, even though my cable worked fine before (and so did the port). Guess I have two dead cables here, because the third one did the trick.
Drivers installed at once, Android installed and I feel very stupid now. Thank you very much for being so patient with something this stupid.
Click to expand...
Click to collapse
Had that problem before too. Glad you got it sorted.
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
JJ2197 said:
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
Click to expand...
Click to collapse
It is not bricked. I'm still not convinced you are on jellybean bootloader as there is not a version of Cwm that works with it and you still have cwm.
First thing you need to do is confirm what bootloader you are on before you really brick it.
Switch the machine on and look where the tegra logo is. If it is bottom center you are still on ICS bootloader and if it is bottom right it is jellybean bootloader.
We need to know this to point you to the correct version of twrp to flash to start.
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
JJ2197 said:
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
Click to expand...
Click to collapse
Really you are going to need to get into fastboot and get the drivers installed.
I'm guessing you know how to get into fastboot but if you don't then hold down volume down and power button for 10 seconds when off. When the icons appear press volume down to go over to the USB icon and then press volume up. It will freeze on the prime screen at this point and that is fastboot mode.
Now go into device manager and try to install naked drivers. If this does not work then try in on another pc. If this still does not work then you have a faulty cable. A faulty cable can still charge the tablet but will not work in pc.
At this moment my money is on your cable being faulty over something you said earlier about having to play with it. You can buy a replacement cheaply on eBay.
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
JJ2197 said:
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
Click to expand...
Click to collapse
Without getting any drivers installed at all there is not much we can do.
Cwm doesn't support external cards and even tho I could make you a flashable zip to install twrp you couldn't get it on there.
If you can get back into the machine at all then we could use wireless adb and send the files over that way or use es file explorer to access network shares and take them over.
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
JJ2197 said:
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
Click to expand...
Click to collapse
This normally happens with a faulty cable and as you said you think the pins are faulty so it could be that instead.
You could try going to the wipe icon where the fastboot icon is and try running that. If there is a rom still on there it will try to factory reset but I can't guarantee that will work but at this point you have nothing to lose.
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
JJ2197 said:
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
Click to expand...
Click to collapse
I'm not talking about in CWM. I'm talking about the wipe icon where the fastboot icon is also.
Isn't the factory reset the same in both CWM and bootloader?
JJ2197 said:
Isn't the factory reset the same in both CWM and bootloader?
Click to expand...
Click to collapse
No
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
JJ2197 said:
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
Click to expand...
Click to collapse
It reformats the partitions back to stock except the system partition.
I'm not saying this is going to work for you. Just as you are your only other option if the pins are broke is to get it sent back to asus and they will swap out the whole mobo so you might as well have a go.