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.
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.
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
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
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!
The device works properly. I was able to unlock the bootloader using flashtool. The problem is, I can't get it into fastboot mode. I hold volume up, plug in the usb cable, it does a quick flash from amber to green, then nothing. From what I'm reading, it's supposed to stay lit blue. So something isn't right here, but it doesn't seem like the steps can be screwed up.
As a point of reference, I tried re-flashing the factory FTF, and even installing a different one. The results are the same. Device boots fine, but I can't access recovery or bootloader(most importantly).
Any help would be greatly appreciated!
InGeNeTiCs said:
The device works properly. I was able to unlock the bootloader using flashtool. The problem is, I can't get it into fastboot mode. I hold volume up, plug in the usb cable, it does a quick flash from amber to green, then nothing. From what I'm reading, it's supposed to stay lit blue. So something isn't right here, but it doesn't seem like the steps can be screwed up.
As a point of reference, I tried re-flashing the factory FTF, and even installing a different one. The results are the same. Device boots fine, but I can't access recovery or bootloader(most importantly).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
have you try flashtool command to command your phone go to fastboot mode automatically if you on flash mode?
Nicklas Van Dam said:
have you try flashtool command to command your phone go to fastboot mode automatically if you on flash mode?
Click to expand...
Click to collapse
Yes, of course. Using the flashtool does not work, neither does using adb reboot-bootloader.
InGeNeTiCs said:
Yes, of course. Using the flashtool does not work, neither does using adb reboot-bootloader.
Click to expand...
Click to collapse
i think this hardware issue, but have try it another way like from your reboot option from system?
Nicklas Van Dam said:
i think this hardware issue, but have try it another way like from your reboot option from system?
Click to expand...
Click to collapse
I just don't understand how my bootloader can be broken, but everything else still works?
I need to know how to fix this in order to move forward.
InGeNeTiCs said:
I just don't understand how my bootloader can be broken, but everything else still works?
I need to know how to fix this in order to move forward.
Click to expand...
Click to collapse
i don't know too, may be you need help from reconigzed developer or any senior member. i think like that
Thread closed until the OP checks his PMs and tells me which device he has
Install drivers from c:\flashtool\drivers
and choose fastboot, flashmode and z drivers
When you unlocked using flashtool did you get the code from sony?
Also, dial *#*#7378423#*#* goto service info and configuration, what does the last line say exactly
gregbradley said:
Thread closed until the OP checks his PMs and tells me which device he has
Install drivers from c:\flashtool\drivers
and choose fastboot, flashmode and z drivers
When you unlocked using flashtool did you get the code from sony?
Also, dial *#*#7378423#*#* goto service info and configuration, what does the last line say exactly
Click to expand...
Click to collapse
I'm on a mac, I got my unlock code from sony, and the last line says "Bootloader unlocked: Yes"
I can try it on a pc, but the problem isn't the method, it's the device. ADB correctly sends the reboot-bootloader command, it just doesn't get to the bootloader. I get a black screen. Same for when I try and access recovery. It's just really odd that the device still works this way.
Would trying this on a pc with the drivers listed be any different? I'm at work now and I can use my PC instead of my macbook if it'll yield different results.
InGeNeTiCs said:
I'm on a mac, I got my unlock code from sony, and the last line says "Bootloader unlocked: Yes"
I can try it on a pc, but the problem isn't the method, it's the device. ADB correctly sends the reboot-bootloader command, it just doesn't get to the bootloader. I get a black screen. Same for when I try and access recovery. It's just really odd that the device still works this way.
Would trying this on a pc with the drivers listed be any different? I'm at work now and I can use my PC instead of my macbook if it'll yield different results.
Click to expand...
Click to collapse
What were you expecting? There is no bootloader screen on the phone. You get a black screen when in fastboot mode, all commands are done from a command window on the computer.
Have you installed a recovery? If not then you cannot enter it. There is no factory or stock recovery accessible on xperia phones.
I would suggest using a Linux or windows machine, I have heard of nothing but problems using macs.
Is there any way I can reflash the factory bootloader with an ftf? I've done two so far and it hasn't seemed to help anything.
To my understanding, when the device is off, you hold volume up and then plug the usb cable in. This should make the led stay solid blue, but mine just blinks amber then green real quick, and nothing happens.
Can someone confirm that I'm not crazy here? It's not like this is my first time modifying an android device. I've been using android since the G1, I work as an IT manager, I use windows, mac, and ubuntu linux regularly, I've compiled my own roms from aosp...So this is really making me nuts!
gregbradley said:
What were you expecting? There is no bootloader screen on the phone. You get a black screen when in fastboot mode, all commands are done from a command window on the computer.
Have you installed a recovery? If not then you cannot enter it. There is no factory or stock recovery accessible on xperia phones.
I would suggest using a Linux or windows machine, I have heard of nothing but problems using macs.
Click to expand...
Click to collapse
The entire process worked fine up until trying to get into fastboot mode. Everyone is saying I should see a blue led, but that's not happening, and it doesn't respond to fastboot commands on my mac, and the pc installer doesn't install the drivers. I've tried searching for the driver files, but I'm not having any luck. I don't want an installer, I just want to manually select the windows driver files and force it to install.
Windows 8.1, latest version of flashtool, my device just shows up in device manager as c6833. When I tell it to search for drivers, it doesn't find anything even after having run the driver installer. Is there a website or a thread on xda that has just the driver files for the z ultra rather than a full installer?
Progress: I've pulled the driver files out of the installer. I'm going to try and get the device recognized on my pc in a bit.
InGeNeTiCs said:
Is there any way I can reflash the factory bootloader with an ftf? I've done two so far and it hasn't seemed to help anything.
Click to expand...
Click to collapse
Not sure what you mean, you have not altered the bootloader, just unlocked it. Also, flashing FTF's do not touch the bootloader
To my understanding, when the device is off, you hold volume up and then plug the usb cable in. This should make the led stay solid blue, but mine just blinks amber then green real quick, and nothing happens.
Click to expand...
Click to collapse
Yes, phone off, keep volume up pressed and attach USB cable (Volume down would be for flashmode) I think you have issues with the drivers on a mac
Can someone confirm that I'm not crazy here? It's not like this is my first time modifying an android device. I've been using android since the G1, I work as an IT manager, I use windows, mac, and ubuntu linux regularly, I've compiled my own roms from aosp...So this is really making me nuts!
Click to expand...
Click to collapse
You are not crazy, You can also try
Code:
adb devices
to see if the machine sees the phone when it is turned on, then try
Code:
fastboot devices
to see if it is actually in fastboot mode or not
InGeNeTiCs said:
The entire process worked fine up until trying to get into fastboot mode. Everyone is saying I should see a blue led, but that's not happening, and it doesn't respond to fastboot commands on my mac, and the pc installer doesn't install the drivers. I've tried searching for the driver files, but I'm not having any luck. I don't want an installer, I just want to manually select the windows driver files and force it to install.
Windows 8.1, latest version of flashtool, my device just shows up in device manager as c6833. When I tell it to search for drivers, it doesn't find anything even after having run the driver installer. Is there a website or a thread on xda that has just the driver files for the z ultra rather than a full installer?
Click to expand...
Click to collapse
The installer with flashtool is quite good, you can choose which files to use,
Just pick the fastboot, flashmode and Z drivers
gregbradley said:
Not sure what you mean, you have not altered the bootloader, just unlocked it. Also, flashing FTF's do not touch the bootloader Yes, phone off, keep volume up pressed and attach USB cable (Volume down would be for flashmode) I think you have issues with the drivers on a macYou are not crazy, You can also try
Code:
adb devices
to see if the machine sees the phone when it is turned on, then try
Code:
fastboot devices
to see if it is actually in fastboot mode or not
The installer with flashtool is quite good, you can choose which files to use,
Just pick the fastboot, flashmode and Z drivers
Click to expand...
Click to collapse
also note that on windows 8.x you have to be in the special boot mode to install unsigned drivers
Just curious did u manage to make ur phone work cuz I got similar problem with recovery(TWRP) it sometimes only show it rest of time it's black screen and in that black screen I can tap on reboot to system or poweroff. It's annoying sometimes cuz I need to flash some important stuff.