Related
Hey
First question:
Ive searched on the net about root but i cant find it, anyone who can help me?
Second question
Ive tried to sim unlock the phone with this guide:
http://sanfranciscoandroid.co.uk/an...-unlock-the-orange-san-francisco-ii-for-free/
but no luck, i get error when im using the unlock tools....
"line 1 failed please reset the modem manually" and ive looked on the web what that means but i cant find anything.
Modell: Blade II
Android version: 2.3.6
Basebandversion: P735TB01
Kernalversion: 2.6.38.6
Version: GB_p735TV1.0.0B03
Anyone who can help me with this ?
I have the same issue, there's currently no root/CWM available for our phone.
Maybe sebastian404 from the Modaco community might be working on one.
https://twitter.com/Sebastian404
eljelali said:
Hey
First question:
Ive searched on the net about root but i cant find it, anyone who can help me?
Second question
Ive tried to sim unlock the phone with this guide:
http://sanfranciscoandroid.co.uk/an...-unlock-the-orange-san-francisco-ii-for-free/
but no luck, i get error when im using the unlock tools....
"line 1 failed please reset the modem manually" and ive looked on the web what that means but i cant find anything.
Modell: Blade II
Android version: 2.3.6
Basebandversion: P735TB01
Kernalversion: 2.6.38.6
Version: GB_p735TV1.0.0B03
Anyone who can help me with this ?
Click to expand...
Click to collapse
Root method available on Modaco:
http://www.modaco.com/topic/355835-zte-blade-ii-released/page__pid__1992958__st__20#entry1992958
Use fastboot method from this page:
http://blog.podtwo.com/android/recovery/ClockworkMod%20Recovery%20for%20ZTE%20Blade2.html
All the files you need(ADB, fastboot, including recovery.img for the Blade II-> thanks to Sebastian404):
http://cl.ly/2F2B3Y0O2G45
Some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ignore
Sent from my Blade using Tapatalk 2
[email protected] said:
Alternative way of flashing CWM w/o a pc: http://www.modaco.com/topic/350343-alternative-way-to-flash-recovery/
Sent from my Blade using Tapatalk 2
Click to expand...
Click to collapse
TPT Helper doesn't support the Blade II (yet) so that will just brick your phone.
Blade II =! OSF2/T-Mobile VivaCity/Blade S
Lol ive already bricked my phone, when i reboot it i go to the green android, there is no recovery and i dont think i can use the adb, is the phone ****ed now ?
sui785 said:
TPT Helper doesn't support the Blade II (yet) so that will just brick your phone.
Blade II =! OSF2/T-Mobile VivaCity/Blade S
Click to expand...
Click to collapse
Tpt helper does support the crescent/ blade2 and the vivacity as I have used it plenty or times, not sure about blade s if that's what you mean!
Sent from my ZTE-BLADE using Tapatalk 2
bladebuddy said:
Tpt helper does support the crescent/ blade2 and the vivacity as I have used it plenty or times, not sure about blade s if that's what you mean!
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
Dude you don't understand, the Blade 2 is a different phone(it has a 1ghz arm v7 processor), look it up on the internet(its only being sold in Sweden and in Belgium).
Sent from my Galaxy Nexus using Tapatalk 2
sui785 said:
Dude you don't understand, the Blade 2 is a different phone(it has a 1ghz arm v7 processor), look it up on the internet(its only being sold in Sweden and in Belgium).
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I do understand there's a phone out called blade 2. I was under the impression that it was being referred to as the blade s to try and stop confusion with the zte crescent referred to also as the blade 2. It's my mistake as I should of read what firmware his phone was running in the opening post.
Sent from my HUAWEI U8815 using Tapatalk 2
Root / Clockworkmode SUCCESS
Hi
I managed somehow to install clockworkmode and to root the phone.
So i was having problems like many others that "waiting for device" message and nothing happened .
I fixed this issue and i like to inform ,help others whos still fight with this problem.
This message is have to do with the zte drivers in windows , so everithing is just cause drivers !!!
So i'm using Win 7 64bit and now i tested at my office also on Win 7 32bit (both ultimate) and it worked.
What you need to download Recovery.img , superuser , usb drivers , from modaco webpage or there is in some other sites !
1. i extracted the 'adb_fastboot_and_other_tools.zip' to c:\ so we have C:\Android\
2. I append the C:\Android\ in the ENVIROMENT VARIABLES at PATH clicked EDIT then after the paths append ;C:\Android\ (copyed here the recovery.img and , Superuser-3.2-RC2-arm-signed.zip to the phone SD)
3. On my blade2 checked the USB DEBUGGING settings then connected to computer
4. At this point i opened the DEVICE MANAGER to see allthetime what happening with the phone drivers
5. I installed the usb drivers mentioned abowe. (and i was looking at device man to ensure that there is no error in drivers)
6. At this point i opened a COMMAND PROMPT from c:\android\ then i checked my phone with 'ADB DEVICES' command ,... list of devices attached P735T was written
7. now i type 'ADB REBOOT BOOTLOADER' then the phone after 5-7 sec reboots to the Green android screen and stuck there
8. At this point my device manager lost ZTE HANDSET MODEM, ZTE COMPOSITE ADB INTERFACE devices and found a new one ,ANDROID with driver error !!! Important to set the DEVICE ISTALLATION SETTING in windows to use INSTALL DRIVERS FROM WINDOWS UPDATE IF NOT FOUND ON MY COMPUTER
9. i choosed UPDATE DRIVER from DEVICE MANAGER , and updating from the internet , after a while it found a driver and installed , and i got finally a working device named ZTE BOOTLOADER INTERFACE or whatever it was
10. At this point i checked with ADB DEVICES my phone , but dont worry its not seeing like before , but its communicating anyway !
11. so I typed the 'FASTBOOT FLASH RECOVERY RECOVERY.IMG' then it starts the process ,after 3-4 sec its finished.
12. now typed 'FASTBOOT REBOOT'
13. Phone restarts normally , then powered off , battery taken out for 10 sec , power button pressed for a while.
14. Restarted the phone by holding the Power button and Volume Down buttons until i entered in clockworkmode recovery !
15. Then i used INSTALL ZIP FROM SD CARD and choosed the Superuser-3.2-RC2-arm-signed.zip , flased and rebooted after.
16 Phone restart normally , i used ROT CHECK to check if my device is rooted , you found on the market.
17. YESS my phone have clockwork and rooted WOOW
---
gjenck said:
Hi
I managed somehow to install clockworkmode and to root the phone.
So i was having problems like many others that "waiting for device" message and nothing happened .
I fixed this issue and i like to inform ,help others whos still fight with this problem.
This message is have to do with the zte drivers in windows , so everithing is just cause drivers !!!
So i'm using Win 7 64bit and now i tested at my office also on Win 7 32bit (both ultimate) and it worked.
What you need to download Recovery.img , superuser , usb drivers , from modaco webpage or there is in some other sites !
1. i extracted the 'adb_fastboot_and_other_tools.zip' to c:\ so we have C:\Android\
2. I append the C:\Android\ in the ENVIROMENT VARIABLES at PATH clicked EDIT then after the paths append ;C:\Android\ (copyed here the recovery.img and , Superuser-3.2-RC2-arm-signed.zip to the phone SD)
3. On my blade2 checked the USB DEBUGGING settings then connected to computer
4. At this point i opened the DEVICE MANAGER to see allthetime what happening with the phone drivers
5. I installed the usb drivers mentioned abowe. (and i was looking at device man to ensure that there is no error in drivers)
6. At this point i opened a COMMAND PROMPT from c:\android\ then i checked my phone with 'ADB DEVICES' command ,... list of devices attached P735T was written
7. now i type 'ADB REBOOT BOOTLOADER' then the phone after 5-7 sec reboots to the Green android screen and stuck there
8. At this point my device manager lost ZTE HANDSET MODEM, ZTE COMPOSITE ADB INTERFACE devices and found a new one ,ANDROID with driver error !!! Important to set the DEVICE ISTALLATION SETTING in windows to use INSTALL DRIVERS FROM WINDOWS UPDATE IF NOT FOUND ON MY COMPUTER
9. i choosed UPDATE DRIVER from DEVICE MANAGER , and updating from the internet , after a while it found a driver and installed , and i got finally a working device named ZTE BOOTLOADER INTERFACE or whatever it was
10. At this point i checked with ADB DEVICES my phone , but dont worry its not seeing like before , but its communicating anyway !
11. so I typed the 'FASTBOOT FLASH RECOVERY RECOVERY.IMG' then it starts the process ,after 3-4 sec its finished.
12. now typed 'FASTBOOT REBOOT'
13. Phone restarts normally , then powered off , battery taken out for 10 sec , power button pressed for a while.
14. Restarted the phone by holding the Power button and Volume Down buttons until i entered in clockworkmode recovery !
15. Then i used INSTALL ZIP FROM SD CARD and choosed the Superuser-3.2-RC2-arm-signed.zip , flased and rebooted after.
16 Phone restart normally , i used ROT CHECK to check if my device is rooted , you found on the market.
17. YESS my phone have clockwork and rooted WOOW
Click to expand...
Click to collapse
Hi,
this manual is copied from xxxxxxxxxxxxxxxxxxxxx (I can not post the link, try to google "356968-guide-how-to-rooting-your-zte-blade-ii" and it really works!! I've tested it. Respectively it is not copied, the user who solved problem (gjenck) with "android interface device driver" post his reply also here.
There is important notice: when rebooted to bootloader, the device really change from "zte blade" to "android interface device". I have windows vista and there was no "update online" option for the driver. So I googled "android device driver" and find it. It seems to be some generic android usb driver.
Karel
kz233 said:
Hi,
this manual is copied from xxxxxxxxxxxxxxxxxxxxx (I can not post the link, try to google "356968-guide-how-to-rooting-your-zte-blade-ii" and it really works!! I've tested it. Respectively it is not copied, the user who solved problem (gjenck) with "android interface device driver" post his reply also here.
There is important notice: when rebooted to bootloader, the device really change from "zte blade" to "android interface device". I have windows vista and there was no "update online" option for the driver. So I googled "android device driver" and find it. It seems to be some generic android usb driver.
Karel
Click to expand...
Click to collapse
Yess thats guy is me i posted also on other forums, the original howto it was frome someone else found in many variants on the net , but it wont work , and when i solved the problem with the driver i made a new howto based on the original and my experience too
Good to know that its working on vista too ...
But my big problem is that i have just 150 Mb storage in my blade II so do you saw somewhere any info how to unlock more storage space like in blade 1 ????
That would be nice to have in Blade II
gjenck said:
Yess thats guy is me i posted also on other forums, the original howto it was frome someone else found in many variants on the net , but it wont work , and when i solved the problem with the driver i made a new howto based on the original and my experience too
Good to know that its working on vista too ...
But my big problem is that i have just 150 Mb storage in my blade II so do you saw somewhere any info how to unlock more storage space like in blade 1 ????
That would be nice to have in Blade II
Click to expand...
Click to collapse
Root it and make a partition on ur sd card, use link2sd to link ur apps and u have more space. That's what I did on my Blade II
Sent from my Galaxy Nexus using Tapatalk 2
sui785 said:
Root it and make a partition on ur sd card, use link2sd to link ur apps and u have more space. That's what I did on my Blade II
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi
I already rooted and i put clockworkmode and made a partition 1gb on sd , cant remember ext2 or ext3 or ...
but if i start link2sd and asking for ext partition whatever i choose its giving Mount script error Mount script cannot be created Write:no space left on device
!!!
So whats now ...
gjenck said:
Hi
I already rooted and i put clockworkmode and made a partition 1gb on sd , cant remember ext2 or ext3 or ...
but if i start link2sd and asking for ext partition whatever i choose its giving Mount script error Mount script cannot be created Write:no space left on device
!!!
So whats now ...
Click to expand...
Click to collapse
Try wiping cache first
I tried but the same
I formatted the ext3 , then wipe cache partition but the same.
Another strange thing in Blade II that the accelerometer is bad !!!!!!!!!!!
Its shaking a lot and the orientation is confused its something really wrong , i have 1 week old blade II and today i tried anothert new one at the shop and its the same bad sensor
Anybody noticed this on Blade II ???
Maybe with new Kernel or FW if thay make we will solve the problem !?
Thank you
so thank you for the root.
Is it android ics for this phone with a custom rom?
thank you so much
Please read this
http://forum.xda-developers.com/showthread.php?p=34022803
Asus TF300T | ZTE Blade
hogsim said:
so thank you for the root.
Is it android ics for this phone with a custom rom?
thank you so much
Click to expand...
Click to collapse
I think someone should be able to port a rom from the blade iii or g300 they have exactly same hardware!
can someone do that? or is it really hard to do?
Link to the latest readback extractor thread
It is applying for mtk6260A watch phones as GT08, DZ09, GV08, T7, Iradish Y6, Q8, F8 and all variations
In short - if you intend to install in your smartwatch new firmwares, mods etc, before to initiate any flashing with the Flash Tool app (pushing that goddamn < Download > button) think twice, 'bove all better DO a backup for the original firmware, why so? because it's containing all original drivers hence you'll be able to recover 100% your watch in case of bricking.
How to:
First you have need of a full dump of your ROM. Assuming that you already got a Flash Tool 5.1308 and drivers, and you were at the point of flashing something (already chose the download agent and scatter file)
for instance let's say you have a DZ09 smartwatch:
1 - press < Readback > in upper menu and so < Add > in the middle menu
2 - click twice on the item appears in the main window, set name as ROM_DZ choose in browser the path and save
3 - set as Physical start address 0x00000000 and as Length 0x01000000 then ok
4 - press < Readback > in the middle menu wait 2 seconds and connect through USB your watch
5 - wait until the upload is complete (big green ring)
Now second stage:
1 - download the app I've built attached here (Readback Extractor mtk6260A 1.0.rar) and unzip it
2 - create a folder where you intend to keep in safe the original firmware and name it for instance DZ09-Orig
3 - do a copy of Readback Extractor mtk6260A 1.0.exe and place it inside the DZ09-Orig folder then click twice on it
4 - press <Load Readback file> and browse after the ROM_DZ file created before with the Flash Tool then open
5 - Wait about two minutes while the app will check bit by bit the integrity of your file
6 - If everything went ok and your file is healthy app will show " health 100% " so you can proceed to next step
7 - Press <Rebuild Firmware> and wait about 5 to 10 minutes (it has a progress counter there)
8 - When will appear the message " - ALL DONE!!!" close app and go back in the DZ09-Orig folder, now you'll find there 5 new files which are the original firmware kit ready to be flashed back in your phone anytime you want
AFTERWARDS READ ME story - Anywhere you search, there is no one to tell you explicitly how to extract from your mtk smartwatch the firmware kit
All says a halfmouth: Do a full < Readback > in Flash Tool, you'll do it being confident that from now on you say goodbye to any risk because you have A BACKUP hence you start flashing new firmwares. And the Big Brick is coming , you smile and get back to your < Readback > backup discovering that, sadly, you have a binary bulk at first sight good for nothing. It cannot be so useless, isn't it? after all it contains full dump of your ROM! I was in exactly the same situation, so 'cause I didn't find any answer I've started reverse engineering . . . and it worked, first I did it manually for guys being in the same situation, 've noticed that is a common issue so I had to choose how to help, simpler but dangerous (for you) way, to create a tutorial <how to> or the hard way (hard for me), to develop an app which will do all "cooking" automatically and I choose the second because in manually way there is a quite big "chance" to mess up with your primary bootloader which could get to a real tragedy - no modem - brickest brick you saw in your entire life
thanks
thank you very much!!! I was searching how to backup my firmware and I found this forum!! Thank you! Thank you! Thank you!
make video pls!!
hello, please make video how you backup dz09 smartwatch original firmware!! PLEASE!! Thank You!!!
flagerchika said:
thank you very much!!! I was searching how to backup my firmware and I found this forum!! Thank you! Thank you! Thank you!
Click to expand...
Click to collapse
Very wise decision to backUP your firmware! Let me know how things goes
gugesha said:
hello, please make video how you backup dz09 smartwatch original firmware!! PLEASE!! Thank You!!!
Click to expand...
Click to collapse
Unfortunately, my time is quite limited,follow the steps in tutorial, if anything is unclear ask here
Thank you Golem_ for this nice tut.
Unfortunately with my GT08 the FlashTool doesn't seem to start the Read Back process. I see the watch in device manager (COM4), installed the MTK VCOM drivers. I can even access the AT interface of the watch (when the watch is powered on).
The steps i tried to perform are..
1) power off the watch
2) start flash tool, start the Read Back
3) connect the watch via usb --> COM4 appears in device manager
4) flash tool detects watch on COM4 port
5) nothing further happens - Read Back won't start (not even after 1 hour of waiting)..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried with FlashTool v5.1308.00.00 and even the latest v5.1524.00 from spflashtool.com. Same result..
any clues?
dominic1134 said:
Thank you Golem_ for this nice tut.
Unfortunately with my GT08 the FlashTool doesn't seem to start the Read Back process. I see the watch in device manager (COM4), installed the MTK VCOM drivers. I can even access the AT interface of the watch (when the watch is powered on).
The steps i tried to perform are..
1) power off the watch
2) start flash tool, start the Read Back
3) connect the watch via usb --> COM4 appears in device manager
4) flash tool detects watch on COM4 port
5) nothing further happens - Read Back won't start (not even after 1 hour of waiting)..
I've tried with FlashTool v5.1308.00.00 and even the latest v5.1524.00 from spflashtool.com. Same result..
any clues?
Click to expand...
Click to collapse
you have to load a scatter file from a compatible firmware (just for initialization, not for flashing)
Golem_ said:
you have to load a scatter file from a compatible firmware (just for initialization, not for flashing)
Click to expand...
Click to collapse
yep, loaded the scatter from the firmware over here http://www.needrom.com/download/gt08-mt6260a-2/
dominic1134 said:
yep, loaded the scatter from the firmware over here http://www.needrom.com/download/gt08-mt6260a-2/
Click to expand...
Click to collapse
still not working? that's weird!
Golem_ said:
still not working? that's weird!
Click to expand...
Click to collapse
yep it is kinda weird...
dominic1134 said:
yep it is kinda weird...
Click to expand...
Click to collapse
Try a RAM test (be aware, only RAM!), who knows, maybe your watch is on 64Mb
Golem_ said:
Try a RAM test (be aware, only RAM!), who knows, maybe your watch is on 64Mb
Click to expand...
Click to collapse
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.
dominic1134 said:
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.
Click to expand...
Click to collapse
Flash tool has to be set on Options / USB Download/Readback and BackUP and Restore on no action
Please does anyone have the stock ROM file for apro q18 smart watch
Unable to carry read back or memory test
Hi Golem,
Firstly please accept my appreciation for your indepth analysis and details that you have been sharing on forum..
I have been scratching since yesterday evening to do readback and install drivers , but am unable to do it succesfully. It I add drivers from device manager and then run the run back I get following error:
FLASHTOOL ERROR : S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] Can not pass bootrom start commabd! POssibly target power up too earlu.
[HINT]
Can you please help? I am scratching and trying various things - but I guess am missing something on the installation side... Tried installing with different versions including WIN XP Service pack2,3 etc. but no success... Same error when I run Memory test to check if indeed the drivers have installed..
vir25 said:
Hi Golem,
Firstly please accept my appreciation for your indepth analysis and details that you have been sharing on forum..
I have been scratching since yesterday evening to do readback and install drivers , but am unable to do it succesfully. It I add drivers from device manager and then run the run back I get following error:
FLASHTOOL ERROR : S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] Can not pass bootrom start commabd! POssibly target power up too earlu.
[HINT]
Can you please help? I am scratching and trying various things - but I guess am missing something on the installation side... Tried installing with different versions including WIN XP Service pack2,3 etc. but no success... Same error when I run Memory test to check if indeed the drivers have installed..
Click to expand...
Click to collapse
Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Issue not resolved yet...
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST[/QUOTE]
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
---------- Post added at 09:54 AM ---------- Previous post was at 09:34 AM ----------
vir25 said:
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
[/QUOTE]
Dear Golem - My Skype id is: viral.gosalia, can we skype chat?
vir25 said:
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
---------- Post added at 09:54 AM ---------- Previous post was at 09:34 AM ----------
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
[/QUOTE]
Dear Golem - My Skype id is: can we skype chat?[/QUOTE]
sent you a message in skype
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
flashtool error
i get the same erro annyone pls help
looks like same problem as Dominic, flashtool just sits waiting. Any solutions
Any solutions not already tried, multiple ports, computers, baud rates cables mem test etc.
dominic1134 said:
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.
Click to expand...
Click to collapse
This guid shows two things:
1. How to enable QPST and USB diag mode.
2. How to enable rSAP.
Please notice, I'm not responsible for any damage in hard- and software of your devices, if you are following this guid. You do all on your own risk.
Click to expand...
Click to collapse
For this guid your device have to be rooted.
In the newer versions of OnePlus' CyanogenMod diag mode is disabled in kernal. Therefore you have to flash an earlier ROM. In this step download Calkulin's Stock Rooted XNPH44S ROM and store zip to your device.
Go to recovery and make a full backup. This is really necessary to preserve the state of your phone.
Wipe Dalvik Cache, System, Data and Cache. ATTENSION: This will delete all your settings, apps and app data!
Install XNPH44S ROM
After rebooting system go to Settings -> About Device -> tab ten times on Build-Number to unlock developer settings. Than go to Developer settings and make sure USB debugging is enabled.
Download the package, containing driver and QPST
Connect your device to USB, go to Settings -> Storage -> USB computer connection and deselect both MTP and PTP.
For Win8 and Win10: restart with deactivated driver signature check.
Open ADB (Android SDK) and type following commands:
Code:
adb shell
Code:
su
Code:
setprop sys.usb.config diag,adb
Go to Windows Device Manager and open Other Devices node. There are two entries of our device "A0001". Klick right on the first one and choose Update driver software -> Browse my computer... -> Let me pick from a list... -> Show all devices -> Have disk -> Browse...
Browse to folder Driver in downloaded package, than open Win x64 or Win x86 corresponding to your system, select *.inf file and apply.
After seccessful installation there is a Modems node in Device Manager, containing node HTC USB Modem. Right click and go to Properties. In top of the Modem tab page is the information about used COM-port. Remember that COM<number>.
Go to QPST folder in downloaded package and execute setup.exe to install QPST.
Open QPST Configuration from windows Start menu, go to Ports tab page and click on Add New Port.... Type (the remembered) COM<number> to the "Port:" text box and OPO to the "Port Label:" text box. Than click on OK.
Active Phones tab page should now look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can use QPST.
Open EFS Explorer from windows Start menu. It may take a moment to read data from your device.
On left side you can see a folder tree like in file explorer. Navigate to /nv/item_files/modem/qmi/uim
Click right on right side and than Copy Item File from PC. Browse to EFS Entry folder of downloaded package and choose file sap_security_restrictions.
Close all windows and reboot your device. If you want, you can repeat the steps 10, 16 and 17 to verify success.
Boot to recovery and restore your backup.
Now go to Google Play and download app Bluetooth SIM Access Install and app Bluetooth SIM Access (Trial)
Open Install app and click on Install system files. The phone have to reboot after installation. If you want to verify successful installation, open app again, the desintall button have to be enabled now.
Enable your Bluetooth
Open Bluetooth SIM Access (Trial) app go to Settings -> Check SIM Access. If there no errors and several entries with green check marks, than rSAP is working now.
Files:
Package (On Mega click on 'download in browser')
ROM (On Mega click on 'download in browser')
Acknowledgement:
Thank you devilsshadow, for your tutorial, which showed me how to setup QPST.
Thank you Calkulin, for your ROM, which makes it possible to use QPST.
Special thanks goes to Martin , for developing his great apps and making our phones better.
Great! Thanks a lot!
Finally got my OPO working with my VW premium bluetooth car system
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Edit:
Got it to work with the Frankenstein modem from here:http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Looks like it does not work with the newer modems, i was using bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
Hi, do you have further informatiom about the crash? Exact error message?
Did you try windows compatibility mode?
I used win 8.1 x64. Sorry I don't have win 10 to test it.
I used Win 10 Pro 64bit, and had no problems using the software.
Thank you very much for the precise description! I linked it from android-rsap
With my newly acquired OPO I first could not install the diag drivers. The USB id seems to have changed from VID_05C6&PID_6765&MI_00 to PID_676C. After changing that in the inf file the installation worked and I could run QPST.
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
I'm wondering about this myself.
I was running jgcaap CM13 before I did enable RSAP. Took a backup of everything in TWRP first. And restored everything except EFS after (thought that if I flashed EFS I would loose rsap again, but I'm not sure). Everything is working fine btw
fitzpete said:
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Click to expand...
Click to collapse
This seems to happen with more recent baseband versions. They require the "Factory Test Mode" (ftm_mode) to be set to allow changes. ftm_mode is NV item 453. It can be modified with the QXDM tool.
Now the value of ftm_mode is cached inside the baseband software. Currently I don't know a better solution than to reboot the phone. Sadly in some phones (OnePlus 2) the value doesn't survive the reboot.
Mugen_Civic said:
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
Click to expand...
Click to collapse
Yesterday I do enable RSAP, wow I am really happy about that.
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Gesendet von meinem A0001 mit Tapatalk
hums87 said:
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Click to expand...
Click to collapse
No. RSAP will stay enabled.
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Thanks for the hint. I will reupload it soon and give an announcement.
mamath53 said:
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Click to expand...
Click to collapse
I reuploaded the files to other hoster.
Could someone tell me what this is good for?
Flatric said:
Could someone tell me what this is good for?
Click to expand...
Click to collapse
RSAP (remote SIM access protocol) is a communication standard for free speeking systems. Eg. Volkswagen concern uses it in its cars. The SIM of your phone is cloned per bluetooth to your cars build in mobile phone module. The radio functions (calling/SMS) are disabled on your phone while connection and executed by your car. That is good for battery, electro smog in your car and connectivity.
But it have drawbacks too. No internet connection on phone while connection. This problem is solved in newer cars by providing a wifi hotspot, which uses the internet contract of your SIM.
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
r0tati0n said:
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
Click to expand...
Click to collapse
Hi, I think the check has moved to the installer app. See section 3.
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
r0tati0n said:
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
Click to expand...
Click to collapse
I think so. Test it with your car. Thats the reason why the trial app exists. But you have to know that the trial app swaps numbers in contact, therefore it is not good for all day use.
I haven't uninstalled the installer app. In this app you can see updates for the system files. But the updates are seldom and if the installed version works for you, I think it's no problem to uninstall it.
In this Thread i will explain how to set up MTK drivers and Flashtools.
Guideline:
Post #1 : Set up MTK drivers in Windows 8 / 8.1 / 10
Post #2 : Use Flashtools for MTK Devices
Post #3 : How to Root Stock Rom
Post #4 : Windows 10 MTK Drivers installation ( just in case post #1 dont work )
Post #5 : Lost IMEI Backup
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Install MTK drivers in Windows 8 / 8.1 / 10
what we need:
MTK Vcom Preloader Driver 2.0
Download : https://www.androidfilehost.com/?fid=24438995911977169
First thing we need is to Disable the Signed Driver verification on Windows :
To disable driver signature verification, we’re going to need to get into the Troubleshooting options from the boot manager.
The easiest way to bring this screen up is using this secret trick.
Hold down the SHIFT key while you click Restart.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once your computer has rebooted you will be able to choose the Troubleshoot option.
Then head into Advanced options.
Then Startup Settings.
Since we are modifying boot time configuration settings, you will need to restart your Computer one last time.
After restarting your computer a second time,
choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
That’s all there is to it. Your PC will then reboot and you will be able to install unsigned drivers.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Now its Time to open SP_Driver_v2.0.zip and start the DriverInstall.exe
it will open the install prompt . Press okay and dont change the installation path
Code:
C: // program files / Mediatek / Driver Package
during the installation it will start the verification window security.
Click on Install this driver software anyway
There will be an Error Message . - We Ignore it !
-Now Open your Device Manager and leave it open.
-Power Off your Phone and connect it with your Pc.
-you will see Under ports ( COM & LPT ) a Preloader unknown device
right click on there and click on Driver update/installation.
-Choose manually search for drivers
-Browse to C:// program files / Mediatek / Driver Package and apply.
-If all went good you have successfully installed the MTK Vcom Drivers. :good:
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Use Flashtools
i use SP_Flash_Tool_Windows_v5.1520.00.000 and never had a problem with it.
Its for most all MTK Phones and for all Elephone Devices
Download Link: https://www.androidfilehost.com/?fid=24438995911977217
- Extract the Flashtool zip folder to your Desktop
- Click flash_tool.exe to open the Tool
- You will see two "folder buttons" Download agent and Scatter-loading
- Into Download agent place the MTK_AllInOne_DA.bin file .
its in your Flashtools folder
- Into Scatter-loading place the Scatter.txt
All Stock Roms / Custom Recoverys have one Scatter.txt in their Zip files.
- Make sure that every partition is checked
-IMPORTANT NOW, Flashing Part-
-Power Off your Device!
-Press on the Download Button!
-Connect your Device with PC and wait until all is flashed
-you will see a Green Mark when all is done
-Disconnect your Device and press Power button to Reboot.
:fingers-crossed::good::fingers-crossed:
------------------------------------------------------------------------------------------------------------------------------------------------
How to Root Stock Rom
-If you want to Root your prefered Stock Rom
-Place SuperSU into your Sdcard
-Flash a Custom Recovery with Flashtools and its Scatter.txt
-Hold Vol+ and Power to get into Bootloader Menu
-Navigate with Vol+ and apply Recovery with Vol-
-Flash Supersu.zip
-Reboot
Stock Roms:
Stock ROM Elephone P9000_Android 6.0_20160315 Link: http://bbs.elephone.hk/thread-9967-1-1.html#[email protected]
CWM Recovery:
Link : https://www.androidfilehost.com/?fid=24459283995304518
100% bug free Supersu v.2.46.zip
https://download.chainfire.eu/696/SuperSU/
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers
Lost IMEI Restore
A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/
MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?
I'm having same issue here on Win10 installed the drivers etc... using latest SP Tools plug phone in and try and put recovery as a download nothing happens.
EDIT: Nvm got it working realised I was downloading and plugging in the phone in the wrong order.
Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#
#LOUDmouth# said:
Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#
Click to expand...
Click to collapse
False positive
kopasz93 said:
MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?
Click to expand...
Click to collapse
I have a solution for restoring IMEI:
In the dialer: *#*#3646633#*#*
OR
download "MTK engineering mode" app and start it
it will open engineering mode:
1/ go to "Connectivity" tab
2/ go to "CDS information"
3/ go to "Radio information"
4/ then select "Phone 1"
5/ At the top there is a command line "AT+" in it
6/ type AT+EGMR=1,7,"your imei number" (for example: AT+EGMR=1,7,"012345678901234")
7/ then hit "Send at command" (if you got error try to put space between "AT" and "+")
8/ go to "Phone 2" and type in the command line: AT+EGMR=1,10,"your imei"
9/ hit "send at command"
10/ restart your phone and it should work
You can check if it changed at Settings -> About Phone -> Status -> IMEI information
If your forgot your original IMEI numbers you can find them on the box of the phone
MTK droid tool recognizes my phone, but do not get the green button so root error. Granted permission in supersu.
If anyone is still struggling (like me) with the error: Initializing scatter file failed. Please check the name of the scatter which you load is legal
i solved by using SP Flash Tool 5.1552.00.000 downloaded from
https://mega.nz/#!ixdnhDLK!oOaAsJrcvJI0vH3fTsUOYjtDxQ_HT61E-_iuo6fTuKk
as specified in elephone forum flashing guide
http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0
Use latest v5.162 version
Gesendet von meinem P9000 mit Tapatalk
Linux way?
Is there a way to root my brand new P9000 in Linux?
I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?
sundawn said:
I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?
Click to expand...
Click to collapse
Why on earth are you using such an old version of SuperSU?
You are probably using TWRP 3.0.0 which does not work on newer ROM versions. Try flashing TWRP 3.0.2-1.
Well i used it because it is said to work in this tutorial
The newer one didnt work either, as you said i think its the TWRP 3.0.0
I would like to download this http://www.needrom.com/download/twrp-3-0-2-1-4/
but i dont get any registration mails, tried to register with 2 different emails half an hour ago...
The version here on XDA is said to be only for P9000 Lite.
Edit: Ok got my login by using the forgot password function - the linked TWRP 3.0.2 and installing SuperSU 2.65 works.
Thanks!
also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?
n1ck75 said:
also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?
Click to expand...
Click to collapse
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk
skeleton1911 said:
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
Thanks for the prompt reply;
Have got to the fastboot oem unlock part, gives option for
Vol Up - Unlock
Vol Down - Cancel
Vol Up doesn't work? Can only Vol Down
For Ze500CL only! If you got No Fastboot, No recovery, No Display, hard bricked your device.You must perform sequential steps indicated below, process will include many small steps. Plz make sure to perform all steps in same sequence and same manner as prescribed. Remove all drivers related to mobile you have installed earlier.
Step 1: Install the driver and connect mode IntelSocUSB IntelSoc:
This Is the driver which help a computer connecte to your Zen2 IntelSoc mode. To install these driver you need to perform special steps if you are using windows 8 / 8.1, 10 . you need to disable driver signature enforcement before installing drivers. below i have mentioned steps needed to install driver for various versions of windows. but first download the needed driver from link given below.
https://drive.google.com/open?id=0B72QQTXqZSRwR0JGeFI2U3FUZ2c
Step 1.1 - how to install these drivers:
If you're using Windows 7:
Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc.
If you're using Windows 8 / 8.1 :
On Keyboard press Windows + I to show charm bar in the right corner,
click on the option setting. Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This will reboot windows and allows you access to the advanced mode, now select the following options: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
now you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
If you're using Windows 10 :
On Keyboard press Windows + I or click Start, select Settings.
In The Settings window, select the Update & security.
Continue Choose recovery and click "Restart now".
When The computer has access to the Advanced screen you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
1.2 Connect Zenfone with computer IntelSoc Mode:
Now you must complete this step before installing xfstk downloader. it helps to setup device's connection to PC
on your pc open device manager and find Intel Soc.
Click to expand it. You will see a single option under here.
Connect your phone to computer via USB cable,
now back to the phone, hold power button for 10 seconds to shutdown completely, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds. it will add an item immediately below intelSoC in device manager “MOOREFIELD” new devices is connected successful.
Now Download intel android USB Driver and install normally from link below:
https://drive.google.com/open?id=0B72QQTXqZSRwSU5CdDNuUElEcUE
1.3 Installing xfstk-downloader:
installation of xFSTK is very simple. download xFSTK setup from the link below. to install. right click the setup file and run as Administrator. click next next simply until you finish the download process
Here is the download link:
https://drive.google.com/open?id=0B72QQTXqZSRweDdfMjlPOGEyTW8
Now to Unbrick Process.
Using xFSTK to unbrick the Device:
Required Files:
https://drive.google.com/open?id=0B72QQTXqZSRwRTRCMlJJcVB2a2M
After downloading the necessary files extract it. It will contain 5 files which will be used to bring your phone back to life.
Now Run xFSTK as Administrator. Now click “CLVP A0 / B0 / B1” last option bottom right hand.
Then Go to Options to change the value of gp flag. Tick GP value over ride, in the Value Section change value to 0x80000245. Now tick Include softfuse file. And select the file Named “signed_CLVP_CSAP_SoftFuseFile_PF450CL” from extracted files. Change the detection timeout value to 180. And click okay.
Now select Firmware files FW DnX: and IFWI: by clicking small three dots:- CLVp_CSAP_FWR_DnX_20.3E.bin and IFWI_v91.15_CSAP_MFG.bin from extracted
Now select operating system: OS DnX - CLVp_CSAP_OS_DnX_20.3E.bin, OS image - droidboot.img.POS_sign.bin from extracted files.
Now see the Device Status section below, this section shows the number of connected target (devices) , you need at least one device is connected., if not try hold power button for 10 seconds to make sure it power downs completely. then hold the volume down button and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds.
As you see connected target. Click begin download to start implementation. You may get error multiple time. But repeat the process again and again. Untill you see FW+OS download complete.
After that you may seea 4 color, just like some TV stations stop broadcasting on TV. You have to wait a little. after few seconds or minutes device will boot into bootloader. If not repeat the xFSTK process again.
Flash Raw Firmware Using Asus Flash Tool:
Required Files:
Asus Flash Tool: https://drive.google.com/open?id=0B72QQTXqZSRwUDZqa0M4SWRObVE
Raw Firmware File: https://yadi.sk/d/LNzLj8mMyytyL
Download Asus Flash Tool and install. Run asus flash tool as administrator. And select the phone model. Then select the downloaded raw file and click start button to flash.
Note: sometimes flash process may go endless. If this happens remove the usb from computer. Kill asus flashtool process from task manager. Now run tool again and flash.
Hi dude, thank you very much for your guide and your help but I still have some problems that I cant resolve.
Firstly in order to make my phone detected by my pc i need to powercycling it pressing "Power + vol up" and not down as you mentioned. I followed any step of your guide but every time I click begin download the bar under the usb logo on my phone it became red and the download did not complete and abort it self. Did you know how to solve this issue ?
waltermaffy said:
Hi dude, thank you very much for your guide and your help but I still have some problems that I cant resolve.
Firstly in order to make my phone detected by my pc i need to powercycling it pressing "Power + vol up" and not down as you mentioned. I followed any step of your guide but every time I click begin download the bar under the usb logo on my phone it became red and the download did not complete and abort it self. Did you know how to solve this issue ?
Click to expand...
Click to collapse
as i mentioned in my guide. very first of all remove all kind of mobile related drivers and xfstk tood if you already installed. it is very important to install soc driver before installing xFSTK. moreover before installing xFSTK and after installing isoc driver you need to power cycle and connect your device to pc. and use volume down button. change the right flag value. and when using xfstk. load files. click begin download. when it start waiting for device then power cycle it. it will itself force into download.
if i bricked my phone but i can enter fastboot mode can i recover it using the asus flashtool?
fabi.m said:
if i bricked my phone but i can enter fastboot mode can i recover it using the asus flashtool?
Click to expand...
Click to collapse
yes definitely you can do it.. download raw firmware and sew it.. if asus flash tool fails. do tell me. i will try to write manual commands to flash.
sukhwant717 said:
yes definitely you can do it.. download raw firmware and sew it.. if asus flash tool fails. do tell me. i will try to write manual commands to flash.
Click to expand...
Click to collapse
alright, thank you so much. im downloading right now, i'll let you know either way!
Thank you so much! worked perfectly
so after flashing raw fw and booting up it suddenly is carrier locked and is askig for a "SIM network unlock pin" i tried flashing a different ROM and the problem persists.. any suggestions? My device was unlocked previous to this..
fabi.m said:
so after flashing raw fw and booting up it suddenly is carrier locked and is askig for a "SIM network unlock pin" i tried flashing a different ROM and the problem persists.. any suggestions? My device was unlocked previous to this..
Click to expand...
Click to collapse
don't use wrong code. you will lock permanently. i will give you unlock code soon
sukhwant717 said:
don't use wrong code. you will lock permanently. i will give you unlock code soon
Click to expand...
Click to collapse
thank you! i now have my phone unlocked thanks to the code you sent me
help me, my cloverviewplus driver was not installed, any solutions?
xJri17 said:
help me, my cloverviewplus driver was not installed, any solutions?
Click to expand...
Click to collapse
which operating system you are using?
sukhwant717 said:
which operating system you are using?
Click to expand...
Click to collapse
windows 7 32bit
xJri17 said:
windows 7 32bit
Click to expand...
Click to collapse
need to install driver before xFSTK. soc device must be recycled to install driver correctly.
xFSTK. will not open for me. I followed all the steps and I run xFSTK. as Administrator. It asks me if I want to allow it to run. I click Yes, but nothing happens. When I look in Task Manager it is not there?>
My OS is Windows 10.
Any ideas?
sukhwant717 said:
need to install driver before xFSTK. soc device must be recycled to install driver correctly.
Click to expand...
Click to collapse
how to recycling my device?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can't detect my device
Sent from my HTC One M9 using XDA-Developers Legacy app
[/IMG]
Sent from my HTC One M9 using XDA-Developers Legacy app
i have the red bar under usb icon as well.
---------- Post added at 10:42 PM ---------- Previous post was at 10:40 PM ----------
[/COLOR]help help