cloverview plus device driver - Asus Zenfone 5 - General Questions and Answers

Hi, trying to follow this tutorial:
http://www.asuszenfoneblog.com/2014...howComment=1427315377761#c8013971213914520565
but cannot install clover driver.
In device manager under Intel Soc must be Cloverview driver but have no idea what else to do.
It comes up for 1 second and dissapear coz "device is not connected"
Sure, windows update cannot find drivers, i was trying to manualy add drivers, added but same problem.
Don't what else to do for unbrick phone.

http://www.drivermax.com/driver-download/0/INTEL+SOC/Intel+Corp./Cloverview+Device it work me to tab3 P5200

same problem here!
Can anybody help me. PLZZZZZZZZZZZZZZZ

Search: iSocUSB Driver Setup.

Got any solution??
---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------
BuzzFuzz said:
Hi, trying to follow this tutorial:
http://www.asuszenfoneblog.com/2014...howComment=1427315377761#c8013971213914520565
but cannot install clover driver.
In device manager under Intel Soc must be Cloverview driver but have no idea what else to do.
It comes up for 1 second and dissapear coz "device is not connected"
Sure, windows update cannot find drivers, i was trying to manualy add drivers, added but same problem.
Don't what else to do for unbrick phone.
Click to expand...
Click to collapse
Solved?

Related

Nexus S root without a PC

For some reason the computers cannot load the drivers successfully after I connect via USB.
I rolled back on a stock rom and have lost SU and CWM.
I searched around but couldn't find any way of rooting, loading SU and CWM from phone itself.
Help me out on this or how can I fix my USB issue?
rapidreinsta said:
For some reason the computers cannot load the drivers successfully after I connect via USB.
I rolled back on a stock rom and have lost SU and CWM.
I searched around but couldn't find any way of rooting, loading SU and CWM from phone itself.
Help me out on this or how can I fix my USB issue?
Click to expand...
Click to collapse
Yes you can, but it's a long way....
---------- Post added at 09:40 PM ---------- Previous post was at 09:36 PM ----------
I think it is easier to fix your drivers into PC ....
---------- Post added at 09:49 PM ---------- Previous post was at 09:40 PM ----------
Download drivers for Nexus s : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
Just unpack .....
Now conect your phone with PC and navigate into Device Manager and click right on ( Android phone or Nexus S , find something that you have linked to android or nexus ) and choose update driver software -> and now choose Browse my computer for driver software and choose Nexus_S_Drivers_x86_x64 and OK....Good luck !
surdu_petru said:
Yes you can, but it's a long way....
---------- Post added at 09:40 PM ---------- Previous post was at 09:36 PM ----------
I think it is easier to fix your drivers into PC ....
---------- Post added at 09:49 PM ---------- Previous post was at 09:40 PM ----------
Download drivers for Nexus s : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
Just unpack .....
Now conect your phone with PC and navigate into Device Manager and click right on ( Android phone or Nexus S , find something that you have linked to android or nexus ) and choose update driver software -> and now choose Browse my computer for driver software and choose Nexus_S_Drivers_x86_x64 and OK....Good luck !
Click to expand...
Click to collapse
I'll give it a shot. I have tried plugging different cables and tried different PC's.
I just get a message pop up saying driver was not installed successfully.
This may be a issue with USB port of phone. Just a guess right now.
In device Manager it is listed as an unknown device. When I try to update the drivers, it simply says my drivers are up to date.
I have another (New) instance of windows and same result on both.
Tomorrow I'll show you how you can root directaly on the phone because it's a long story...
surdu_petru said:
Tomorrow I'll show you how you can root directaly on the phone because it's a long story...
Click to expand...
Click to collapse
I'll wait. So far I have the terminal app on phone. phone state is unlocked but no SU and Stock recovery. Via stock recovery I dunno how to flash SU..
Once I have SU I can use Rom manager
I downgraded to get ICS OTA. They stopped OTA at the moment.
Solved
I couldn't stop laughing... a stupid step made it work
First I thought it is a hardware issue and took it to Samsung Servce center. The guy replaced my USB port. My phone was out of warranty and he asked for $12 USD.
Bad luck, even changing the port didn't work. The same issue. Guy didn't bill me as issue still remained. He suggested to change some IC / chip. Which didn't go down well with me and I took phone with me.
While my phone was connected to PC, it used to pop up device not compatile message everytime the screen sleeps or waked up. So in 'Settings -> Applications -> Development -> Stay awake' I checked the box.
It worked like a charm, I have notification on the phone, able to access it on PC.
Three words---- LOL
Thanks to those who tried to help.
surdu_petru said:
Yes you can, but it's a long way....
---------- Post added at 09:40 PM ---------- Previous post was at 09:36 PM ----------
I think it is easier to fix your drivers into PC ....
---------- Post added at 09:49 PM ---------- Previous post was at 09:40 PM ----------
Download drivers for Nexus s : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
Just unpack .....
Now conect your phone with PC and navigate into Device Manager and click right on ( Android phone or Nexus S , find something that you have linked to android or nexus ) and choose update driver software -> and now choose Browse my computer for driver software and choose Nexus_S_Drivers_x86_x64 and OK....Good luck !
Click to expand...
Click to collapse
surdu_petru, igot the same issue.
1)fastboot is not recognizing my device and tried with different pc and usb but adb is working fine
2)first time when i rooted my device it went fine after some days flashed factory image(4.1.2)
3)again when i tried to root its not working
4)can you tell me how to flash recovery througn terminal emulator in phone
Have you checked this thread?
http://forum.xda-developers.com/showthread.php?t=2034264

[Q] Root Official v30a

Is there any easy way to root the v30a for an optimus p920 without flashing bootloaders or anything else ? I also need to install CWM too..
Anyone ???
You can install CWM with this tool
http://forum.xda-developers.com/showthread.php?p=37893247
then install root with this, see #5
http://forum.xda-developers.com/showthread.php?p=39130435
but I have not tried it that way myself.
drastic00 said:
You can install CWM with this tool
http://forum.xda-developers.com/showthread.php?p=37893247
then install root with this, see #5
http://forum.xda-developers.com/showthread.php?p=39130435
but I have not tried it that way myself.
Click to expand...
Click to collapse
I just can't install the OMAP4430 drivers as in your guide. I couldn't unbrick my phone either when it was broken. But when I brought my phone to a local service he did it pretty fast. I followed the guide step by step but whatever I do, the OMAP4430 keeps blinking under TI Boards and my windows tries to update the drivers after I install them manually and fails because the device keeps connecting and disconnecting.
I have windows 7 x64 ultimate. Any ideas ?
Nightfallen said:
I just can't install the OMAP4430 drivers as in your guide. I couldn't unbrick my phone either when it was broken. But when I brought my phone to a local service he did it pretty fast. I followed the guide step by step but whatever I do, the OMAP4430 keeps blinking under TI Boards and my windows tries to update the drivers after I install them manually and fails because the device keeps connecting and disconnecting.
I have windows 7 x64 ultimate. Any ideas ?
Click to expand...
Click to collapse
If OMAP4430 device appears for seconds and then disappear in your Windows Device Manager, run a cmd as an admin and type :" SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 " and press enter, then type :" devmgmt.msc " and press enter. Choose View, Show Hidden Devices, you will see now your hidden OMAP4430 device. You may now proceed to the driver installation)
Karim Kahale said:
If OMAP4430 device appears for seconds and then disappear in your Windows Device Manager, run a cmd as an admin and type :" SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 " and press enter, then type :" devmgmt.msc " and press enter. Choose View, Show Hidden Devices, you will see now your hidden OMAP4430 device. You may now proceed to the driver installation)
Click to expand...
Click to collapse
I've been considering adding this to my tutorial as a tip.
You can also quickly right click on it when it appears, as described.
drastic00 said:
I've been considering adding this to my tutorial as a tip.
You can also quickly right click on it when it appears, as described.
Click to expand...
Click to collapse
Yes, this most happens with windows 7 and 8 but still no problem with windows xp.
Karim Kahale said:
Yes, this most happens with windows 7 and 8 but still no problem with windows xp.
Click to expand...
Click to collapse
The reason I have not added this to my guide already is I don't want to write a tutorial on how to use command lines . But, maybe just this little bit is OK .
drastic00 said:
The reason I have not added this to my guide already is I don't want to write a tutorial on how to use command lines . But, maybe just this little bit is OK .
Click to expand...
Click to collapse
I did exactly what you two told me. Still blinking in device manager and keeps connecting and disconnecting.
I guess I'll just sell it and buy an S2 or S3. It's too much to do to it even for a simple root. >.<
Nightfallen said:
I did exactly what you two told me. Stilln ghost entries even when it's not connected which will allow you install the drivers properly. blinking in device manager and keeps connecting and disconnecting.
Click to expand...
Click to collapse
What version of windows are using? You should see omap device in ghost entries in device manager even when the device is not connected which will allow you to install the drivers properly.
If this still doesn't work for you, I am sure that using another pc will solve your problem.
Karim Kahale said:
What version of windows are using? You should see omap device in ghost entries in device manager even when the device is not connected which will allow you to install the drivers properly.
If this still doesn't work for you, I am sure that using another pc will solve your problem.
Click to expand...
Click to collapse
Tried on Windows XP x86, Windows 8, Windows 7 x64 and x86. No luck.
Nightfallen said:
Tried on Windows XP x86, Windows 8, Windows 7 x64 and x86. No luck.
Click to expand...
Click to collapse
Are you sure that you are opening the cmd as admin and checking show hidden devices?
Karim Kahale said:
Are you sure that you are opening the cmd as admin and checking show hidden devices?
Click to expand...
Click to collapse
Yes. I'm not a noob with windows commands and things like this. I did. The sound of connecting/disconnecting persists anything I do. And blinking under TI Boards and Other devices (depends if I install or not the drivers).
Nightfallen said:
I just can't install the OMAP4430 drivers as in your guide. I couldn't unbrick my phone either when it was broken. But when I brought my phone to a local service he did it pretty fast. I followed the guide step by step but whatever I do, the OMAP4430 keeps blinking under TI Boards and my windows tries to update the drivers after I install them manually and fails because the device keeps connecting and disconnecting.
I have windows 7 x64 ultimate. Any ideas ?
Click to expand...
Click to collapse
Be sure all things LG are uninstalled before starting. Any leftover LG drivers from previous connections of phone to pc will cause driver installation problems. Reboot pc, turn off all antivirus, antispyware, etc. Those can cause files you need to become corrupt or not appear. Then begin again. Check all details carefully. You can also run the command Karim Kahale described to stop the blinking if you can't catch omap4430 when it appears.
Unsigned drivers are a pain to deal with. It's fiddly but once you have it right, you can leave it alone and you will be ready for Fastboot, LG Flash Tool, Smartflash, ADB, or whatever.
drastic00 said:
Be sure all things LG are uninstalled before starting. Any leftover LG drivers from previous connections of phone to pc will cause driver installation problems. Reboot pc, turn off all antivirus, antispyware, etc. Those can cause files you need to become corrupt or not appear. Then begin again. Check all details carefully. You can also run the command Karim Kahale described to stop the blinking if you can't catch omap4430 when it appears.
Unsigned drivers are a pain to deal with. It's fiddly but once you have it right, you can leave it alone and you will be ready for Fastboot, LG Flash Tool, Smartflash, ADB, or whatever.
Click to expand...
Click to collapse
I did absolutely everything you said. Same blinking.
Nightfallen said:
I did absolutely everything you said. Same blinking.
Click to expand...
Click to collapse
If you are following my tutorial then something was missed or skipped.
---------- Post added at 02:50 PM ---------- Previous post was at 02:28 PM ----------
One more thing, run all installers as administrator if your pc account is not set up that way.
drastic00 said:
If you are following my tutorial then something was missed or skipped.
---------- Post added at 02:50 PM ---------- Previous post was at 02:28 PM ----------
One more thing, run all installers as administrator if your pc account is not set up that way.
Click to expand...
Click to collapse
I only got my user on PC, so it's administrator. I also ran all installers with administrator rights. I`m not missing and skipping anything and I DO restart everytime it says there. No luck.
Battery out of phone.
Run the command lines Karim mentioned. They must be entered exactly. The blinking will stop and you can proceed with installing omap driver. Then you must disconnect and reconnect again with vol up to let LG drivers take.
Hi Guys
last nite I finally upgraded my phone to ICS ( 30 a rom ) from GB
Now in order to root my phone can I use the easy way procedure called MEGATRON ROOT ? I think is very easy to use it!
Please advise
Thanks!!!
Mark

howto: factory mode - preloader

Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
MarvinFS said:
Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
Click to expand...
Click to collapse
Why not contact the CM team?
donalgodon said:
Why not contact the CM team?
Click to expand...
Click to collapse
Would you be so kind to point the correct way to contact 'em on that particular matter?
MarvinFS said:
Hi all,
Anyone have info about how to access factorymode or preloader in OnePlus One?
The Oppo's vol+up way doesn't work!
Maybe the original flash tool and drivers by any chance?
I'm making a preparations to help revive hardbricked phones, is case one have a partitions full dump of cause!
I tried to ask the official forum - but it's totally lame! They even don't understand what is a bootloader and a preloader...
Click to expand...
Click to collapse
Yes i know, its like by LG's, while pushing vol + and vol - just plug the usb cable, but thats where im stuck too. We need the right drivers for that, find 5's drivers wont work, tired already. As you know without right diag drivers, we cant go to next level, hope youll help here
os_man said:
Yes i know, its like by LG's, while pushing vol + and vol - just plug the usb cable, but thats where im stuck too. We need the right drivers for that, find 5's drivers wont work, tired already. As you know without right diag drivers, we cant go to next level, hope youll help here
Click to expand...
Click to collapse
Actually we do have drivers, in a preloader mode the device is detected as
Qualcomm HS-USB Diagnostics 9008
the drivers are here
https://yadi.sk/d/Um0Nk1FIWR6vK
or here
https://yadi.sk/d/5XdeaZFvMBpQ6
but QPST is not working - MDM port is not opened! One guru from our Russian forums found a way to open MDM port, but for ZTE Nubia phones... and it's not working with OnePlus. Needs further research!
Actually all Qualcomm based devices must be somewhat similar in terms of low level flashing!
MarvinFS said:
Actually we do have drivers, in a preloader mode the device is detected as
Qualcomm HS-USB Diagnostics 9008
the drivers are here
https://yadi.sk/d/Um0Nk1FIWR6vK
or here
https://yadi.sk/d/5XdeaZFvMBpQ6
but QPST is not working - MDM port is not opened! One guru from our Russian forums found a way to open MDM port, but for ZTE Nubia phones... and it's not working with OnePlus. Needs further research!
Actually all Qualcomm based devices must be somewhat similar in terms of low level flashing!
Click to expand...
Click to collapse
About ZTE Nubia phones you can ask me everything, i can even write imei to them, ZTE GRAND S II too, and no, they are different. QPST is not working becouse cant connect to the phone in download mode ( sees in download mode ). I will try these drivers now too, if it sees as "HS-USB Diagnostics 9008" might be ok, becouse normaly its HS-USB QDloader 9008 without right driver, if i manualy turn it to 9006, qpst can connect, but this mode is for bricked phones i think ( as in oppo finf 5, in this mode oppo's own service program can write to phone.)
---------- Post added at 07:50 PM ---------- Previous post was at 07:37 PM ----------
Sadly no, i had tried these drivers too, its still QDLoader, not Diagnostic port, we need the diag drivers from the Manufacturer i think, not generic from Qualcom, and i must add i believe this mode is not we are looking for, phone must be online for Qpst to be able to make changes, so we need the right dial code for engineer-service menu (or somewhere hidden in *#808#, all in chineese, still trying to figure it out if its there )
---------- Post added at 08:04 PM ---------- Previous post was at 07:50 PM ----------
"I'm making a preparations to help revive hardbricked phones", can be used if phone is bricked maybe, to download all the sytem to the phone again ( as in Oppo Finf 5 same example again ), but i need a working Qpst that actualy connect to phone "online".
---------- Post added at 08:40 PM ---------- Previous post was at 08:04 PM ----------
pm me for further instructions please..

onelplus one is hard bricked :(

hi all,
i made a mistake when i flash twr recovery before i unlock the phone, than as the others i had the issue when bootloader is locked, when i try to unlocked it, it go to twr recovery by it self.
than i make my mistake when i had erase the all data using twr recovery , after all the phone never start again :crying:
i can't open fastboot ( is totally dead )
i did try :
- color.zip
- also : https://forums.oneplus.net/threads/...ne-from-hard-brick.184927/page-2#post-8186847
and nothing was worked
please please help
when i used ( Color.zip) i install the drive and it shows ( Qualcomm HS-USB Diagnostics 9006)
but when i used the Msm8974DownloadTool the line where is my phone is connected is stay in RED color !!!!
hy my friend. you have a total brick and you stuck in qualcomm emergency mode.
I habe a tool to repair your partition.
Install the correct qualcomm hsusb driver and pm me.
i will repair your partition
konsolen said:
hy my friend. you have a total brick and you stuck in qualcomm emergency mode.
I habe a tool to repair your partition.
Install the correct qualcomm hsusb driver and pm me.
i will repair your partition
Click to expand...
Click to collapse
hi reallly
i install ( Qualcomm HS-USB Diagnostics 9006) is it this one ?
if it is not. please send me the right one
repeair
hy my friend. you have a total brick and you stuck in qualcomm emergency mode.
I habe a tool to repair your partition.
Install the correct qualcomm hsusb driver and pm me.
i will repair your partition
---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------
normaly the qcom mode are only 5 sec active.
open device manager and put usb in. the device will pop up for 5 sec so you must in this 5sec right click and update driver. then select the qualcomm driver.
---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------
After the 5sec the device is not so see because it is in automated DL mode.
Thats my turn then. I try to repair the boot partition that you get normaly in recovery.
konsolen said:
hy my friend. you have a total brick and you stuck in qualcomm emergency mode.
I habe a tool to repair your partition.
Install the correct qualcomm hsusb driver and pm me.
i will repair your partition
---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------
normaly the qcom mode are only 5 sec active.
open device manager and put usb in. the device will pop up for 5 sec so you must in this 5sec right click and update driver. then select the qualcomm driver.
---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------
After the 5sec the device is not so see because it is in automated DL mode.
Thats my turn then. I try to repair the boot partition that you get normaly in recovery.
Click to expand...
Click to collapse
ok i just did
what the next ??
konsolen said:
hy my friend. you have a total brick and you stuck in qualcomm emergency mode.
I habe a tool to repair your partition.
Install the correct qualcomm hsusb driver and pm me.
i will repair your partition
---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------
normaly the qcom mode are only 5 sec active.
open device manager and put usb in. the device will pop up for 5 sec so you must in this 5sec right click and update driver. then select the qualcomm driver.
---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------
After the 5sec the device is not so see because it is in automated DL mode.
Thats my turn then. I try to repair the boot partition that you get normaly in recovery.
Click to expand...
Click to collapse
it shows now (( Qualcomm&Prod_MMC_Storage USB Device ))
is that what you mean ?
MazyooN77 said:
it shows now (( Qualcomm&Prod_MMC_Storage USB Device ))
is that what you mean ?
Click to expand...
Click to collapse
i just solve the issue

Revive of DEAD HONOR 9! (HARDBRICK) (NO TURN ON/CONNECT USB) - SOLUTION!!. (PICTURES)

Hello,
I finaly found out a method how to establish USB-Connection with a "dead" honor 9 (wasn't recognized by computer/didn't turn on/just nothing).
WARNING!! YOUR warranty will be lost IF YOU OPEN HONOR 9!, no guarantee you get anything fixed/Maybe you break more!!
So I show you how I did it:
1: Open the Honor 9 Back: Tutorialvideo (not made by me)
https://www.youtube.com/watch?v=SUI5sA99nDw
- I used Hair Dryer + Knife to open the back. But use the tools in this video if you have.
2: - Install right USB-Drivers.: I needet the drivers "ASC-Driver_Handset WinDriver 2.01.00.00.exe" - You can find them in google!
3. - Connect the 2 Test Points like in my images. I used the SIM-Card tool from the phone to do it.
4. - Connect phone via USB - if everything gone right it shows up in the device manager as "HUAWEI USB COM 1.0"
5. - NOW We need an app or method to flash FirmWare in this mode... actually not supported by DC-Phoenix.... If any solution I edit in the thread.
6. UPDATE UPDATE! PHONE GOT REVIVED READ SECOND POST!
UPDATE UPDATE !
- HONOR 9 REVIVED FROM THE DEAD
- Downloaded DC-PHOENIX (dc-unlocker.com) ->Made Account/Charged Credits
- Connect the Phone via Testpoints, than open DC-Phoenix APP
- Flashed ( Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB ) ->You can find it in DC-Phoenix search.
-> Phone got revived. (NO MORE Huaway boot animation - I got strange red and green colors instead)
-> Open H9 in Fastboot mode (Turn phone off than: VOL+Down + USB CABLE PUT IN)
-> OPEN DC-PHOENIX
-> FLASHED "Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Austria_Poland_Denmark_Finland_Czech_Republic_Hungary.APP" with DC-Phoenix.
[UPDATE 2}
- You have to restore IMEI/SN/CARRIER AND COUNTRY AFTER UPDATING (empty board) with HCU Client - (You can find the software on dc-unlocker.com)
- THAN INSERT SIM CARD TO GET OFFICIAL OTA UPDATES.
-> 100% back to stock with full OTA, everything working, boot animation also back
What could be the reason of those death ? planned obsolescence ? Virus ? just HW problem / quality ? no luck ? ........
sonneper said:
What could be the reason of those death ? planned obsolescence ? Virus ? just HW problem / quality ? no luck ? ........
Click to expand...
Click to collapse
Failure in playing and experimenting with the Software.
ok , nevermind, you manage it ! good play : ) !
yz8_1337 said:
Do you also think this works with mine which bootloops after downgrading from Oreo to Nougat?
Click to expand...
Click to collapse
This should work with all damaged Smarpthones but I also think there are better and much softer techniques to revive looping or software side errors where the phone still turns on.
Maybe try via fastboot mode? But no OT please there are enough threads for it bro.
Revive via testpoints should always be the last option to revive a phone.
I tried this and doesnt work for me, it doesnt even show up as unknown device in device manager.
does anyone know why or is my phone completely dead?
SusKuN1337 said:
I tried this and doesnt work for me, it doesnt even show up as unknown device in device manager.
does anyone know why or is my phone completely dead?
Click to expand...
Click to collapse
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)
4r44444 said:
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)
Click to expand...
Click to collapse
i got told yesterday that the motherboard is broken, so, rest in peace honor 9 :<
I updated my phone with HuRUpdater and no my phone won't turn on. I wanted to locate the ASC-Driver_Handset WinDriver 2.01.00.00.exe, but all of the links are false download links. Can someone point me to a valid link for the driver? Thanks!
Rapid81 said:
I updated my phone with HuRUpdater and no my phone won't turn on
Click to expand...
Click to collapse
Did you save your recovery.log in TWRP after you flashed with HuRUpdater ?
Update from Build to which build ?
On which cust region ?
Rapid81 said:
I wanted to locate the ASC-Driver_Handset WinDriver 2.01.00.00.exe, but all of the links are false download links. Can someone point me to a valid link for the driver? Thanks!
Click to expand...
Click to collapse
Here is ASC-Driver_Handset WinDriver 2.01.02.00.exe :
HUAWEI DRIVER HANDSET PRODUCTLINE 2.01.02.00
https://androidhost.ru/6rf
Please tell us back your experience flashing board software.
oslo83 said:
Did you save your recovery.log in TWRP after you flashed with HuRUpdater ?
Update from Build to which build ?
On which cust region ?
Here is ASC-Driver_Handset WinDriver 2.01.02.00.exe :
HUAWEI DRIVER HANDSET PRODUCTLINE 2.01.02.00
https://androidhost.ru/6rf
Please tell us back your experience flashing board software.
Click to expand...
Click to collapse
No, I did not saved the log. The update went well, no error or any difference. I updated my phone with HuRUpdater several times without problem.
I updated to STF-L09C432B376, but I had problems with that firmware and I went back to B371, as I did before, when I had issues with B374 as well.
Everything went well, and after B371, I installed Magisk v17, like always, pressed the reboot button and since that, the phone won't turn on.
Thanks for the link!
@Rapid81
As you're stating that after installing the driver, the WIndows sees the phone as "HUAWEI USB COM 1.0" :
So you're good to go, then no need for you to open up your device loonking for test points
---------- Post added at 16:28 ---------- Previous post was at 16:19 ----------
Let's chat via PM as I think I have some tools to replace DC-Phoenix tools which is a license-only. I'd like you to test.
I also liled to know how you managed to get COM1 without openphone and connecting testpoints...
oslo83 said:
@Rapid81
As you're stating that after installing the driver, the WIndows sees the phone as "HUAWEI USB COM 1.0" :
So you're good to go, then no need for you to open up your device loonking for test points
---------- Post added at 16:28 ---------- Previous post was at 16:19 ----------
Let's chat via PM as I think I have some tools to replace DC-Phoenix tools which is a license-only. I'd like you to test.
I also liled to know how you managed to get COM1 without openphone and connecting testpoints...
Click to expand...
Click to collapse
I just installed the mentioned driver, connected the phone and the "HUAWEI USB COM 1.0" showed up.
I wrote back to you.
DC-Phoenix give me an error when writing bootloader. I have a brick now.
Rapid81 said:
DC-Phoenix give me an error when writing bootloader. I have a brick now.
Click to expand...
Click to collapse
Have you tried to physically connect test point?
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
4r44444 said:
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)
Click to expand...
Click to collapse
Flashed ( Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB ) ->You can find it in DC-Phoenix search.
What's it mean? Use what to Flash?
Ccboxes said:
Have you tried to physically connect test point?
Click to expand...
Click to collapse
Yes, several times, with method was 100% worked. The main board died.
Rapid81 is getting its bricked STF honor9 seen as COM3 by windows.
He said he changed it in windows settings to COM1.
But both times it didn't worked with DC-Phoenix or IDT...
Maybe he did not managed something...
oslo83 said:
Rapid81 is getting its bricked STF honor9 seen as COM3 by windows.
He said he changed it in windows settings to COM1.
But both times it didn't worked with DC-Phoenix or IDT...
Maybe he did not managed something...
Click to expand...
Click to collapse
Could you give the IDT and frimware to me?I want to try before DC.
Ccboxes said:
Could you give the IDT and frimware to me?I want to try before DC.
Click to expand...
Click to collapse
IDT 2.0.0.9
https://bi-t.xyz/ozS5cy2kTm
---------- Post added at 06:40 ---------- Previous post was at 06:34 ----------
IDT shoud work with with original BoardSoftware not repacked like DC-unlocker's .dgtks .

Categories

Resources