Related
Hi everybody,
First of all, I apologize for my bad English ^^
Then, as you can see from my title, I have some problem with my Flyer....
I just update my HoneyComb mwakious Flying Rom (I was already on HoneyComb before) and I used it in the following morning and everthing worked, until the following afternoon.... so I was here to ask for help to you....
Nobody can help me ?
Sent from my GT-I9100 using XDA App
boby08 said:
Nobody can help me ?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
If I were you, I would follow instructions on following thread
http://forum.xda-developers.com/showthread.php?t=1358758
The install is using fastboot so it would work for you.
Your flyer is in QDL mode. There is no way to power it off short of opening the device and disconnecting the battery. Based on your description of how you got there it should be fine ok if you let the battery run down so that it powers off completely and then charge and power on again provided you had a working CWM installed. If that doesn't work you will have to send it in for repair.
globatron said:
Your flyer is in QDL mode. There is no way to power it off short of opening the device and disconnecting the battery. Based on your description of how you got there it should be fine ok if you let the battery run down so that it powers off completely and then charge and power on again provided you had a working CWM installed. If that doesn't work you will have to send it in for repair.
Click to expand...
Click to collapse
I tried to disconnect the battery, charge flyer and put it on but it doesn't work... Is there any way to left QDL mode with a program or something else ? :crying:
From what I understand, Qualcomm download mode means that everything is gone, including the ROM and Hboot. Without hboot, you can't recover from this. As globatron mentioned earlier (in December!) you need to send the phone for repair.
HTC Flyer can't enter recovery mode & USB cable is not detecting during unbrick
Dears please help!!!
I think, i have bricked my HTC Flyer (P510e / PG41100) when i was installing new ROM.. I am unable to enter recovery mode or any other booting mode.. The screen is flashing & vibrating some time with HTC's intro & comes with blank screen.. The orange colour (indicator for charging) is blinking always..
I have tried the steps as per the post http://forum.xda-developers.com/showthread.php?p=16190536#post16190536 . But, the USB cable is not connecting properly with PC. And in Command prompt, the ADB devices is not listing properly. It shows USB connection error when i run stock ROM. Tried in another PCs too. But, failed.
Also, the device is getting connected & disconnected continuously. (shows as a removable disc).. .The sae time, in the screen CWM's interface is coming & going.... Not stable. stays maximum 3 - 5 seconds...
Kindly request you to help me to come out from this problem..
Thanks in advance for your help...
Renjith.
renjithsuresh said:
Dears please help!!!
I think, i have bricked my HTC Flyer (P510e / PG41100) when i was installing new ROM.. I am unable to enter recovery mode or any other booting mode.. The screen is flashing & vibrating some time with HTC's intro & comes with blank screen.. The orange colour (indicator for charging) is blinking always..
I have tried the steps as per the post http://forum.xda-developers.com/showthread.php?p=16190536#post16190536 . But, the USB cable is not connecting properly with PC. And in Command prompt, the ADB devices is not listing properly. It shows USB connection error when i run stock ROM. Tried in another PCs too. But, failed.
Also, the device is getting connected & disconnected continuously. (shows as a removable disc).. .The sae time, in the screen CWM's interface is coming & going.... Not stable. stays maximum 3 - 5 seconds...
Kindly request you to help me to come out from this problem..
Thanks in advance for your help...
Renjith.
Click to expand...
Click to collapse
run adb on pc and conect the device (with usb), then type: adb reboot recovery...u should on cwm recovery now...:good:
sdpinsens said:
run adb on pc and conect the device (with usb), then type: adb reboot recovery...u should on cwm recovery now...:good:
Click to expand...
Click to collapse
sdpinsens thanks for your reply.. But, there is an error while processing adb reboot recovery.."error: device not found".. Could you please advise what has to be done next...
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
sdpinsens said:
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
:good: Thanks.. CWM working perfectly. Tablet came back to life.. did the following steps..
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Thanks again for your support...
renjithsuresh said:
:good: Thanks.. CWM working perfectly. Tablet came back to life.. did the following steps..
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Thanks again for your support...
Click to expand...
Click to collapse
ur wellcome.....:highfive:
sdpinsens said:
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Thanks. It's working property.
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
cybrkada said:
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
Click to expand...
Click to collapse
How are you installing it ???
Via flash tool??
And nope your phone won't brick
I disconnected the cord. Turned on the phone and noticed that USB Debugging is ticked/checked. So I repeated the process but I am still getting..
< waiting for device >
What should I do?
soulhackereborn said:
How are you installing it ???
Via flash tool??
And nope your phone won't brick
Click to expand...
Click to collapse
Yes, via Flastool. Yeah my phone did not get bricked! :good:
cybrkada said:
Yes, via Flastool. Yeah my phone did not get bricked! :good:
Click to expand...
Click to collapse
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
soulhackereborn said:
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
Click to expand...
Click to collapse
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
cybrkada said:
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
Click to expand...
Click to collapse
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
soulhackereborn said:
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
cybrkada said:
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
Click to expand...
Click to collapse
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
soulhackereborn said:
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Click to expand...
Click to collapse
I dont see PM here, i think I am still restricted.
see if the link helps, i removed w w w
android.gs/install-clockworkmod-recovery-sony-xperia-s
i'm rebooting them after this.. thanks
LiveSquare said:
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
Click to expand...
Click to collapse
Which drivers? I have already downloaded SDK and I believe the S1 driver is installed yesterday when i unlock the bootloader.
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
cybrkada said:
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
Click to expand...
Click to collapse
Dude as far as I know there is no need to check/ tick USB debugging for fastboot... It's just for flashtool..
Try re -installing the drivers again manually or let windows search over internet...
Finally, i made it! thanks to both of you!
fastboot.exe seems to be corrupted!
Problem solved!
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
cybrkada said:
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
Click to expand...
Click to collapse
Yes ur rooted!!
Thanks!
I'm currently downloading Cyanogenmod ver 9.1. Hopefully it works! Thank you so much buddy! You have been very helpful! If I get problems on flashing CM9.1, i'll contact you , hehe
One of the reminders on isntalling CM9 is:
Make sure that your Xperia S is already running a rooted firmware, and that it has the ClockworkMod Recovery properly installed.
How do I know I have a rooted firmware? Do I still need to flash FTF file?
By the way, I am getting a boot loop from CWM recovery, I cant go to the homescreen, no option to turn off! It only reboots the CWM.
(Still downloading CM9 as of the moment)
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till developer option appear on setting. set enable usb debugging there. and try flash it again.
I can't get anything to start!
~~~~
...Well said:
]
---
~~~~I've try to reflash my device again, but then i couldn't be able to enter to flashmode
~~~~{ with the device off; press vol- and then connect to usb}
~~~~after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
~~~~then i activate dev mode: [usb debuggin and OEM UNLOCK]
~~~and try to get to fastboot mode, but the same results...
~~~~i got my device recognized by {ADB DEVICES}
~~~~but can't get fastboot
-----
.~~~~.. nothing wrong.... except well, i can't enter any -mode- now..
~~~~any help?
~~~~Thanks
Click to expand...
Click to collapse
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.[/QUOTE]
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
did you flashed hole ftf using flashtool or only the mencioned partitions above?
PiSpecialist said:
did you flashed hole ftf using flashtool or only the mencioned partitions above?
Click to expand...
Click to collapse
I still can't enter any-mode, so i haven't flash any ftf
me too
merwinaleman said:
I still can't enter any-mode, so i haven't flash any ftf
Click to expand...
Click to collapse
Same Here - is there no-one willing to help?!?
anyone know how to physically cause a device to self test, or reload defaults, ....or.... boot from sd by shorting a pin OR SOMETHING???
grrr - help:crying:
well... a little progress after 100s of reboot attempts!
i see a HD in the Device manager.
I can't access the disk, but it isn't constantly rebooting..
any one have a suggestion for my next move?
Error 7/24/2016 8:40:41 AM DeviceSetupManager 121 None
Device USBSTOR\Disk&Ven_SONY&Prod_Mass_storage&Rev_0310\YT9115VK6R&0 was configured.
Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.10586.0
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0006
Matching Device Id: GenDisk
Outranked Drivers: disk.inf:GenDisk:00FF2002
Device Updated: false
Parent Device: USB\VID_0FCE&PID_E1AD\YT9115VK6R
...still need help....
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
merwinaleman said:
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
Click to expand...
Click to collapse
dude... PLEASE tell me what mysterious, magical stuff happened?!?!!?!?!? I've been having exactly your issue for days now and can't get past it!!! Please
Ugh. I'm having the same problem. Magical stuff isn't very helpful :/
Boot loop
trechurch said:
~~~~
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.
Click to expand...
Click to collapse
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....[/QUOTE]
I have the same issue. I have an unlocked bootloader and booted with boot.img. everything was fine for a day or two, and when I started to factory reset my phone it is causing bootloop issues. sony logo and black screen. It never appears on my computer when connected to use adb. Any idea on how to fix this?
My mob is not able to flsh the stock rom......der s a error showing cannot open bundle....help me out plz
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Try this, jesus bless you
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
1. Turn off OEM Unlock
2. Keep USB Debugging on
3. Enter Fastboot mode
4. Done
5. Jesus Bless You
Thymue said:
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Click to expand...
Click to collapse
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
iFlashed said:
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
Click to expand...
Click to collapse
also for me :´(
Thales720 said:
also for me :´(
Click to expand...
Click to collapse
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Hi7m3up said:
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Click to expand...
Click to collapse
the drivers are all installed correctly, I tried doing this with the OEM off and on and it did not work
none of the methods works, adb does normal boot
recovery reboot (and other apps) crash or boot normal too
volume (+) and power button only makes the phone vibrate (and sometimes the Sony logo appears)
I can't stress to you enough that Enable Oem need's to be on the "on position" so switch it on (allow the device to be oem unlocked)and leave it alone it's nothing to do with you not being able to get to fastboot. If you trip the frp on your phone you will not be pleased.
with that said with your phone switched on and USB DEBUGGING SWITCHED ON plug into your usb on computer open a command window and input the following command- adb reboot bootloader you will now see your blue light on the phone this means your sony is now ready for you to flash a custom recovery (assuming you have unlocked your bootloader ?)
After trying to install a custom ROM I'm now locked out from my phone and I can't shut it down any more. :crying:
It is in a bootloop between the two pages "Pocophone by Xiaomi - unlocked" and "Fastboot".
ADB doesn't recognize the phone and MI Flash the same problem.
Any help?
Go to fastboot and boot from recovery with this command.
fastboot boot xyz.img
Xyz is ur recovery file name.
Flash stock rom zip and wipe cache and reboot to system.
fastboot on PC is waiting for device, I can't get any connection between phone and pc
gartmann said:
fastboot on PC is waiting for device, I can't get any connection between phone and pc
Click to expand...
Click to collapse
Try reinstalling fastboot drivers
Installed SDK platform-tools (including fastboot drivers) on another pc.
adb devices >> doesn't list any attached device
If I connect another cell phone, it will be listed normally.
Let the device drain all the power,,then charge it again.
Any hint how to force this?
Didn't know, how strong the battery is . Second day to press the power button every 20 seconds to drain power to zero
gartmann said:
Any hint how to force this?
Didn't know, how strong the battery is . Second day to press the power button every 20 seconds to drain power to zero
Click to expand...
Click to collapse
Get it checked at service center. Or try changing the pc or mi flash tool version. These are the only way i know. As you are saying that ut is not responding to the fastboot. It maybe a hardware problem like the problem in type c port. So get it checked