How to set device tampered back to false? - Wileyfox Swift

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

Related

R800i Issues with USB Driver and Bootloader!

Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300

Device will not turn on LG G3 D855 32GB

Hello everyone.
I need your help.
My Device: LG G3 D855 32GB
The device does not turn on, the only thing that appears is because when I connect the device to a PC, I see a driver installed:
RELINK HS-USB QDLoader 9008
I read guides on site here, and I'm trying to order
I downloaded the software BoardDiag 2.9
I downloaded the files to the appropriate TOT
I extracted the files by instructors on site.
I opened the program and I followed the guide and it seems to me an error
Download mode is enabled Mode,
I quickly disconnects from the computer and reconnect the computer and then the moment I am unable to do a test and the results are:
AP CHECK START = PASS
EMMC TEST START
FAILED TO OPEN PARTITION FROM EMMC
TEST ABORTED !!
I tried a lot of tutorials but I can not, it always seems the device is in Download Mode
What can I do more?
Please your help,
Eliran
If you go that way, you will need bunch of other stuff. Here is the link
http://open-freax.fr/guide-unbrick-your-lg-g3/
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
The phone fell
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the comment
The phone fell into the vehicle.
I know the phone is always in Download Mode
The software does not let me do anything and making phone download mode
I did not try to install KDZ.
And I can not open a setup KDZ because the device does not rise and there is no open port.
I only have the port I did above.
Thanks for the help, I worked in the guide and I could not ...
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
I need help please. What can i do
zarfati66 said:
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
Click to expand...
Click to collapse
I need help please. What can i do
The phone woke for a moment ...
zarfati66 said:
I need help please. What can i do
Click to expand...
Click to collapse
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
relink hs-USB Qdloader 9008
ZARFATI6 said:
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
Click to expand...
Click to collapse
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
apur32 said:
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
Click to expand...
Click to collapse
Same situation too, solutions yet?
Hey I have the same problem .
If any of you found the solution please post it here or pm me, I am stuck

Zenfone 2 ZE551ML just bricked or faulty parts?

Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click 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 regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click 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 regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.

problem install driver MOOREFIELD

Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)
The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.

PC cant detect my phone

i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
aidenskcyu said:
i flash pixel experience plus and latest firmware and now my phone stuck in fastboot mode and wont detect on my pc.. i cant see it on device manager either.. whenever i try to restart it goes to stucked twrp logo.. can someone help me here?
Click to expand...
Click to collapse
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
SubwayChamp said:
You just have to update drivers from device manager.
Follow this, you can use the fastboot drivers either from Xiaomi or Google (if you already have them installed)
If you don't have the Android with exclamation mark, you can do it the same as shows the latest image.
Click to expand...
Click to collapse
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
aidenskcyu said:
Before i got stuck in fastboot my phone doesn't really detected in my pc even on other computers with fastboot drivers. USB File Transfer not working too, it's only charging. I'm using Havoc OS 4.8 rom and this firmware.
Click to expand...
Click to collapse
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Use known good data cable!!!
Does the phone see the connection?
Is it configured properly?!!!
Try another port.
Reboot, reboot, reboot...
Event manager, check for error messages.
Disk management>scan for new disks, open from here!
Device management, update driver, rollback driver... reboot.
Meh, play with it...
SubwayChamp said:
And did you try what I posted? Probably you need to check which drivers you have actually installed, some of them are sometimes redundant and not necessary, what you need is the Google ADB/fastboot that it is in the Google site, and regards Xiaomi all is in the Mi flash tool and Mi Unlock tool, see to the option to install the drivers hoping that you don't need the Qualcomm 9008-USB drivers.
Of course, this is assuming that you have a data cable not only a charger cable and the issue is not with the ROM itself.
Click to expand...
Click to collapse
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
aidenskcyu said:
can you give me the file for fastboot? now its showing “Unknown USB Device (Device Descriptor Request Failed)”
Click to expand...
Click to collapse
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
SubwayChamp said:
Are you sure your device is actually in fastboot mode with that issue "Device Descriptor Request Failed"?
The drivers are in the Mi Flash tool, when you install the tools you can see the option to install the drivers that are already included in the Mi unlock tool.
From there, just follow the steps indicated in the pictures to update them.
Click to expand...
Click to collapse
i tried it but it has exclamation mark in android bootloader interface.
aidenskcyu said:
i tried it but it has exclamation mark in android bootloader interface.
Click to expand...
Click to collapse
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Try to install ADB and FastBoot drivers for redmi note 8
If Dosent work text here
SubwayChamp said:
It's not showing here an exclamation mark,
Can you upload the right SS?,
Also Did you install the fastboot drivers either from Mi Unlock tool or Mi Flash tool?
Click to expand...
Click to collapse
yes i did install it
aidenskcyu said:
yes i did install it
Click to expand...
Click to collapse
All is here in this same sequence.
i dont know why i get this error code 10.
aidenskcyu said:
i dont know why i get this error code 10.
Click to expand...
Click to collapse
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
SubwayChamp said:
Upload the same as my pictures 2 and 3 from your device manager, from the picture 2 you can use either from Xiaomi or Google.
Delete that Kedacom USB driver and replace for the proper ones, here you have the right guide https://xiaomifirmware.com/guides-and-tips/delete-kedacom-usb-device-driver-pc/
Click to expand...
Click to collapse
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
aidenskcyu said:
somehow it got detected as android bootloader interface. it got detected too in miflash and tried to flash but i got stucked in flashint system.img. after a while it shows timeout error and after that i flash twrp recovery but i got a message that my battery is very low to flash it. will my phone charge in fastboot? because it keeps bootlooping now if ii dont go on fastboot mode
Click to expand...
Click to collapse
Well, at least you got your device showed, no?
To power off the device you can put it in fastboot mode, after of approximately 10 minutes if the device is not attached to your PC, it'll power off, then you can charge it.
But if your device reacts to the power charger trying to boot to nowhere, then fastboot will charge the battery but very, very slowly.
Do you have bootloader unlocked? Why not flashing it through EDL mode?, you don't need battery power to do that.

Categories

Resources