Hi folks,
I'm desperately searching for some help to get my chinese F9300 / MT6577 back to live. What happened?
Yesterday I've booted into the standard installed boot manager (vol + and power on) to figure out whether or not it offered an option to install a zip. As it only offered to modes (recovery mode and factory mode) and a reboot option, I've decided just to leave the bootmanager by selecting 'reboot'. The deviced rebooted, but fell into a boot loop. On boot it automatically starts recovery mode, at the bottom of the screen a white bar appears, then the display goes off and the phone reboots, endlessly...
But with the combination Vol+ and power on I still can access the boot manager. When selecting 'factory mode' I get the option to run a bunch of tests, and in this mode I still have access to the phone via ADB. By running adb shell and entering 'su' at the prompt I also get root access.
Beside that, there is no way I can access the phone to push another ROM to it. In Odin the device doesn't show up, SP Flash Tool doesn't recognize the device and 'adb push' doesn't have any result as it ends with 'insufficient permissions'. To make things worse, it seems the extra SD-card isn't mounted... :crying:
Any options how to proceed...?
Greetz, Ronald
Some more info... after a night of trial and (a lot of) error it seems the phone goes into meta mode for a second or two (battery in, keep the middle button pressed and plug in the USB connector). During those 1 or 2 second it shows up as COM5 and SP Flash Tool recognizes it. Sadly enough then the connection to the phone drops again...
How can I force the phone to remain connected in this notorious meta mode...?
Any help, tips and tricks are welcome!
Ronald
Sent from my HTC Vision using xda app-developers app
try repair this by volcano box.. your problem is finally solve...
Hm, I don't think so. The tool costs more than the actual phone
Sent from my HTC Vision using xda app-developers app
make it
rbouwens said:
Hm, I don't think so. The tool costs more than the actual phone
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
but you can make more money by the tool for repairing all friends china phones and androids.
its the best tool for chinese:good:
Aqui lo tienes todo
rbouwens said:
Hi folks,
I'm desperately searching for some help to get my chinese F9300 / MT6577 back to live. What happened?
Yesterday I've booted into the standard installed boot manager (vol + and power on) to figure out whether or not it offered an option to install a zip. As it only offered to modes (recovery mode and factory mode) and a reboot option, I've decided just to leave the bootmanager by selecting 'reboot'. The deviced rebooted, but fell into a boot loop. On boot it automatically starts recovery mode, at the bottom of the screen a white bar appears, then the display goes off and the phone reboots, endlessly...
But with the combination Vol+ and power on I still can access the boot manager. When selecting 'factory mode' I get the option to run a bunch of tests, and in this mode I still have access to the phone via ADB. By running adb shell and entering 'su' at the prompt I also get root access.
Beside that, there is no way I can access the phone to push another ROM to it. In Odin the device doesn't show up, SP Flash Tool doesn't recognize the device and 'adb push' doesn't have any result as it ends with 'insufficient permissions'. To make things worse, it seems the extra SD-card isn't mounted... :crying:
Any options how to proceed...?
Greetz, Ronald
Click to expand...
Click to collapse
Look at Here : .movilesdualsim.com/foro/threads/22396-Backup-firmware-SMARPHONE-F9300-mtk6577
Before write www
rbouwens said:
Some more info... after a night of trial and (a lot of) error it seems the phone goes into meta mode for a second or two (battery in, keep the middle button pressed and plug in the USB connector). During those 1 or 2 second it shows up as COM5 and SP Flash Tool recognizes it. Sadly enough then the connection to the phone drops again...
How can I force the phone to remain connected in this notorious meta mode...?
Any help, tips and tricks are welcome!
Ronald
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
most mt6577 devices would go into this mode even without a battery, the reason why it goes off after one or two seconds is that its not recieving any command from spflash tool, i suggest you find the proper firmware of your device load it up in spflashtool after selecting the proper scatter file for your device just click on download, spflashtool would now start to scan all usb ports for your device connected now this is the time to connect your device and after connecting it would show up as comXX on spflashtool and flashing will imimediately start. if successful youll see a green circle and your device will go off of meta mode immadietely after flashing
Related
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Ebony Dubois said:
Okay guys, I think my phone has a soft brick (no boot logos), so I'm trying to do some restoration... but I'm not having much success.
So, I found a solution in XDA (/showthread.php?t=825173&page=3) saying that I should plug my phone in without battery, SD nor chip and disable the "LG Modem" on my Device Manager. Afterwards, start KDZ Updater and configure it to CS_EMERGENCY. Then I should install a 2.1 French firmware and as soon as KDZ finishes I'd plug off my phone, plug it back in and start it in DL mode again, this time flashing a file named "OUT.kdz", which gives back the boot logos.
Problem: KDZ Updater hangs as soon as I press "Start". It simply freezes when it's in CS_EMERGENCY. I have no solution to this whatsoever, and I also have another thread with previous problems I ran into (Soft-Bricked LG GT540 Optimus).
These are the best forums I've found for any kind of phone, so I'm positive I'll get the help I need, even if I might need to wait some time. Kudos to the admins and every member for taking part of such a great community!
Click to expand...
Click to collapse
I've fixed all my issues! I'll paste what I said in another thread. Yay for one-full-year struggles!
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
Recently while flashing alpha version of MIUI marshmallow on my Mi 4w, my phone got completely bricked. Complete brick in the sense, it won't turn on, neither charge nor show any led indication. This guide should work on other phones also.Let's start:-
1) Although it seems like your phone wont turn on, your phone is actually working, it's just it wont show anything on the screen(no display).
Make sure your phone is charged properly(it will charge even if the led doesn't show any indication).
2) Download and install Mi flash tool and then Fastboot file of your device. http://en.miui.com/a-234.html
3) Unzip the fastboot image, a folder containing flash all.bat should appear if not, extract the extracted file again. Winrar should work fine.
4) Now open Mi flash tool(as administrator) and select the fastboot folder from Mi flash using browse option and also select the proper fastboot script according to need.
Note: Flash_all.bat will completely erase your internal storage.
5) Now press volume down(-) and power key to enter into fastboot. Note: it won't show any visual whatsoever but it'll work.
6) Connect your phone to your pc. It should show various flash devices connected to your computer and those devices may continuosly connect and disconnect. If not it'll show QHUSUB_BULK install the driver using device manager.
7) On Mi flash tool, some device name should show on the devices list if not click refresh and try reconnecting the device. Note: If you dont have proper drivers installed on your pc, this procedure won't work.
8) Finally click on flash and flashing will start. It'll take some time. Once done it'll show operation completed successfully.
9) Finally boot your device using power key.
Brick has received QHSUSB_BULK simple. This is the normal and regular encounter. Hardbrick, you must check point.
2ConHeo said:
Brick has received QHSUSB_BULK simple. This is the normal and regular encounter. Hardbrick, you must check point.
Click to expand...
Click to collapse
who said so?
tested and working
that normal check point is a pain in ass to execute in the first place
Thanks a ton.....It helped a lot
thank u...
thank
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.
hammer77 said:
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.
Click to expand...
Click to collapse
did you solve the problem ?
Rajdip said:
Recently while flashing alpha version of MIUI marshmallow on my Mi 4w, my phone got completely bricked. Complete brick in the sense, it won't turn on, neither charge nor show any led indication. This guide should work on other phones also.Let's start:-
1) Although it seems like your phone wont turn on, your phone is actually working, it's just it wont show anything on the screen(no display).
Make sure your phone is charged properly(it will charge even if the led doesn't show any indication).
2) Download and install Mi flash tool and then Fastboot file of your device. http://en.miui.com/a-234.html
3) Unzip the fastboot image, a folder containing flash all.bat should appear if not, extract the extracted file again. Winrar should work fine.
4) Now open Mi flash tool(as administrator) and select the fastboot folder from Mi flash using browse option and also select the proper fastboot script according to need.
Note: Flash_all.bat will completely erase your internal storage.
5) Now press volume down(-) and power key to enter into fastboot. Note: it won't show any visual whatsoever but it'll work.
6) Connect your phone to your pc. It should show various flash devices connected to your computer and those devices may continuosly connect and disconnect. If not it'll show QHUSUB_BULK install the driver using device manager.
7) On Mi flash tool, some device name should show on the devices list if not click refresh and try reconnecting the device. Note: If you dont have proper drivers installed on your pc, this procedure won't work.
8) Finally click on flash and flashing will start. It'll take some time. Once done it'll show operation completed successfully.
9) Finally boot your device using power key.
Click to expand...
Click to collapse
Link not working.
Using another mi flash tool also get nothing. How do I know I get into fastboot?
Already pressed volume down and power button but nothing happened. And checking fastboot devices nothing comes up. Also in mi flash tool nothing.
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 ?)
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
holygoatofsteel said:
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
Click to expand...
Click to collapse
Fixed it, but I'll leave this up for anyone thinking they might have the same problem. I fixed this by flashing the stock ROM again, but with one key difference. Ensure you install all appropriate drivers, and then when you hit download, plug the phone in and attempt to put it into recovery mode. This will open the port just long enough for the flash tool to keep it open, and it will flash as usual.
I'm in a bit of a pickle right here. My friend's P20 Lite got dropped and now the screen is dead. Backlight turns on, but the LCD is really, really broken. I can boot it up and unlock it using his swipe-code (by guessing where the dots are), but I cannot recover his data, because USB debugging is disabled
If I reboot into fastboot mode (Power + Vol Down), I can indeed see it on my PC as a fastboot device, but I can't use that for anything, as far as I know.
If I reboot into recovery mode (Power + Vol Up), adb doesn't work.
If I turn it on, unlock it, and plug in a Type-C to HDMI dongle (with power), it does not mirror the screen onto the display. I know the dongle works, as I've tested it with several devices.
HiSuite detects the device is in recovery mode, but then continues to say the device is not supported for system recovery.
What other options do I have? I can plug in a keyboard after it's unlocked, so maybe it's possible to navigate it that way? Like "press KEY to access settings, press down key 20 times, press enter to enter menu" etc. etc. Unfortunately I don't have a P20 spare laying around, so I can't use that for guidance.
The phone's bootloader is NOT unlocked, so I can't even flash TWRP and get into adb that way.
Hopefully someone can help!
Hi,
I sent you a private message.
I have the same problem. Any help, please?
-Alf- said:
Hi,
I sent you a private message.
Click to expand...
Click to collapse
Hi,
Cloud you maybe help me too? Because I have nearly the same problem. I have a Huawei P20 with a broken screen, the touch does not work and I have a password and therefore I cannot unlock it, I would like to be able to get all the data back from the phone and I have tried in many ways how to do it without being able to use it and the only solution is do it through a computer, I have already tried to activate usb debugging with a program, only it shows me the notification but I can not approve, I checked if there was active ADB but it says it is unauthorized and now I wonder if I should send the phone in recovery mode or fastboot mode so that I can control it from a pc or somehow receive the data, the question is how can I do? I have no idea how fastboot or recovery mode can be and whether it will make me lose everything or not so I would like to make sure by asking an expert, I would be very grateful if you could help me.
Hi.
Do anyone has a solution to this ? I'm in the exact same situation...
- normal mode no adb devices
- fastboot mode works, but... what to do in it ?
- recovery mode, no adb devices, nothing
- download Mode too, "adb devices" list it, but unauthorized... Maybe there is a way to copy a custom thing through SD ?
Need help please :'(
TurtleMaster said:
Maybe there is a way to copy a custom thing through SD ?
Click to expand...
Click to collapse
What do you mean by that?
-Alf- said:
What do you mean by that?
Click to expand...
Click to collapse
When is see on the internet what Download Mode is for, i imagine it's possible to copy a custom firmware/OS on the SD card, and then, install it automatically by this special mode.
I just want to retrieve my data... The only viable solution for the moment, is to buy a new P20 Lite screen and change it...
TurtleMaster said:
The only viable solution for the moment, is to buy a new P20 Lite screen and change it...
Click to expand...
Click to collapse
Exactly.
I would recommend this guide:
https://www.ifixit.com/Guide/Huawei+P20+Lite+Screen+++Frame++Replacement/119776