Related
Hi all,
I'm getting crazy and tired about this KS20.
I tried everything on this mobile but nothing worked and now emergency mode is only mode I can turn on the thing: not even the hard reset works anymore (booting stucks on vodafone logo).
Corona drivers never worked: reading inf file they are for product ID 6061, but my mobile when connected is product ID 6000 and only LGE usb drivers (downloaded thru the LG update agent) are correctly working.
And LGMDP can see the device but not flash procedure can be initialized on it.
Someone could help me with that please?????
Come guys!
Give me suggestions please!
Hello,
Your message is somewhat confusing that we can help you, otherwise there is already post on this type of problem you should first browse the forum looking for info more precise. The first goal is the flash in emergency mode, after everything is possible ...
By.
rickou26 said:
Hello,
Your message is somewhat confusing that we can help you, otherwise there is already post on this type of problem you should first browse the forum looking for info more precise. The first goal is the flash in emergency mode, after everything is possible ...
By.
Click to expand...
Click to collapse
I searched the forum and googled everything but nothing related to that.
As I wrote in my first post I could not install Corona drivers because, weird enough, device is not recognized by them. I had to install LGE usb drivers thru LG Agent update wizard.
So I can not flash thru LMPD.
Thanks for your reply anyway.
What OS do you use? Do you have administrator rights!
I do have administrator rights.
I do confirm anyway that only LGE USB drivers (they are directly from LG, Product ID 6000) are working fine when in emergency mode.... but they are not Corona drivers (ones signed for Product ID 6061) and LDMP is not working because of that.
Do I have a chance to install rom if I'm not using Corona drivers?
No !
What OS do you use?
Windows xp sp2
I can imagine that none had to deal with this firmware version.
I guess I had to throw away this mobile... such a wate!
Thanks anyway.
delphilip said:
I can imagine that none had to deal with this firmware version.
I guess I had to throw away this mobile... such a wate!
Thanks anyway.
Click to expand...
Click to collapse
Try to gain access to a computer with Windows 7 or Vista, the work better with Corona drivers.
Install the drivers first, restart just to play safe, connect your phone in emergency mode (make sure the green LED is on) and wait for driver detection and installation to finish. If the second driver takes too long to install, then just disconnect the phone and reconnect again. Flash in emergency mode as usual.
In case you have lost your IMEI, use the IMEI restoration tool to generate a new .nv2 file.
Keep updating us on how things work out for you.
If you haven't seen it already, try and have a look at this guide: http://forum.xda-developers.com/showthread.php?t=548447
The part about disabling and enabling the LG driver in Device Manager got my computer to recognize the device in emergency mode so I could flash rickou26's newest ROM on there (and by the way, thanks for the ROM, rickou )
Thanks guys ... i will try your suggestions as soon as I'll be at home again (next week)!
MTM said:
If you haven't seen it already, try and have a look at this guide: http://forum.xda-developers.com/showthread.php?t=548447
The part about disabling and enabling the LG driver in Device Manager got my computer to recognize the device in emergency mode so I could flash rickou26's newest ROM on there (and by the way, thanks for the ROM, rickou )
Click to expand...
Click to collapse
I tried the guide last week but it didn't work for me.
I guess this V08h firmware (not seen anywhere on the web) is a lost cause!
Well Hello everyone! i'm new to the site, but always being following a few post, so i'll give as much details as possible so you know what is happening let's get to it then.
PS: I have already rooted a device my ARC S and it was in the first try, i say this just to you guys know i have an idea of how easy the process should be.
I have an Acro S LT26W
6.2.b.1.96
Flashtool (downloaded from the youtube link below) version 9.11 for windows
The unknow sources are ON, and all the options i need for the phone to work with the rooting process
I use windows XP
i'm trying to root the device, i installed the flashtool and its drivers, the sony programs, both of them, the sony companion found the phone, the update service program, well when i do the turn off the phone and doing the flash mode steps, the computer freezes and the phone is never found...
I made the steps here www.youtube.com/watch?v=DSsZ7pAJcew the ones of checking the drivers, the flash tool found the phone on debugging mode (the phone is on)(when i did this it installed abd or something like that driver) but, when i finally load the kernel 211 and prepare the phone to flash mode (turn off the phone, press the volumen down botton, hold and connect the usb) the computer says the semc driver is not properlly installed then i have to reset the computer because it freezes just like the update service.... what might be happening in here? i installed the ACRO S for ICS driver, the fastboot and the flashtool driver (the last two options in the flashtool drivers pack) but the problem is still there...
i have the kernel of this site http://forum.xda-developers.com/showthread.php?t=2418991 and i follow the steps of this site http://forum.xda-developers.com/showthread.php?t=2417672 (pretty sad i even get to 3rd step)
Question... (yes another one)
When i connected the phone to the pc to check if the flashtool driver was properlly instaled (debugging mode on) the icon of "root device" appeared, is there something we can do with it? i mean, maybe another way to root the phone? i spent the last 6 hours reading and trying but nothing worked and it's so easy to root a device if you have the proper tools.. i hope you can help me, its driving me crazy omg...
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Well i have good news and i want to ask you guys to check for this "way to root" because it was pretty stupid because of the easy it is.... ok
Now after i couldn't root the phone the way it is posted here, i was looking at you-tube and found a Spanish video about rooting the device, so i decided to give it a try, and wtf, it worked...
Now the steps are these... the video said that IT'LL WORK FOR ANY XPERIA JELLY BEAM DEVICES
(for installing the ROOT program, turn off your anti virus)
1- Go here www.mgyun.com/vroot download the Chinese rooting program and install it. NO NEED TO KNOW CHINESE FOR THIS.
2- Plug the USB cable to your pc
3- Prepare the phone, debugging mode ON
4- Open the rooting program and plug your phone to the pc with the USB cable
5- Wait until the program do its work and don't touch your phone.
6- Once your phone is done, it'll be automatically restarted and it be rooted
7- check the root with "root checker" or other you like
8- Done.
If you want to delete the Chinese root program in your phone follow the next steps.
1- Download SUPER SU program in your phone
2- Grant SUPER SU program root permissions and update the binary plus select NORMAL mode
3- SUPER SU program will find that there's another root program and it'll ask you witch program do you want to use, select SUPER SU and the chinese program will be deleted.
THAT'S ALL....
PD: Ok, now all that was in spanish i just translate it the best i could, this is the video link if someone wants to see it www.youtube.com/watch?v=raIR4ms6xds&list=PLmMm_rKgxjOpQ58IHzbbp1wgCVoSde692&index=2 again, would like to ask for someone to check this and share the way to root the phones if it is 100% safe and no tricks under the table.
hendrickson89 said:
Well Hello everyone! i'm new to the site, but always being following a few post, so i'll give as much details as possible so you know what is happening let's get to it then.
PS: I have already rooted a device my ARC S and it was in the first try, i say this just to you guys know i have an idea of how easy the process should be.
I have an Acro S LT26W
6.2.b.1.96
Flashtool (downloaded from the youtube link below) version 9.11 for windows
The unknow sources are ON, and all the options i need for the phone to work with the rooting process
I use windows XP
i'm trying to root the device, i installed the flashtool and its drivers, the sony programs, both of them, the sony companion found the phone, the update service program, well when i do the turn off the phone and doing the flash mode steps, the computer freezes and the phone is never found...
I made the steps here www.youtube.com/watch?v=DSsZ7pAJcew the ones of checking the drivers, the flash tool found the phone on debugging mode (the phone is on)(when i did this it installed abd or something like that driver) but, when i finally load the kernel 211 and prepare the phone to flash mode (turn off the phone, press the volumen down botton, hold and connect the usb) the computer says the semc driver is not properlly installed then i have to reset the computer because it freezes just like the update service.... what might be happening in here? i installed the ACRO S for ICS driver, the fastboot and the flashtool driver (the last two options in the flashtool drivers pack) but the problem is still there...
i have the kernel of this site http://forum.xda-developers.com/showthread.php?t=2418991 and i follow the steps of this site http://forum.xda-developers.com/showthread.php?t=2417672 (pretty sad i even get to 3rd step)
Question... (yes another one)
When i connected the phone to the pc to check if the flashtool driver was properlly instaled (debugging mode on) the icon of "root device" appeared, is there something we can do with it? i mean, maybe another way to root the phone? i spent the last 6 hours reading and trying but nothing worked and it's so easy to root a device if you have the proper tools.. i hope you can help me, its driving me crazy omg...
Click to expand...
Click to collapse
I think this is the only way to root acro s in .96 firmware. Rooting is actually very easy if you are familiar with it and it will take around 10minutes to get it done Since you are using .96 firmware, here are the actual steps for rooting your acro s (yes, i have simplified making it more easier to read)
1. install sony pc companion(for the your device drivers of course), fastboot and flash mode drivers
2. flash the .200 or .211 kernel (because the doomlord toolkit only support rooting on acro s with .200 and .211 kernel, the latest .96 did not included, so we need to downgrade the kernel for rooting)
3. root the device using the toolkit
4.flash back the .96 kernel
5.done
Before start, you will need to prepare these things
1. usb cable
2. rooting toolkit(credits to DooMLoRD) http://forum.xda-developers.com/showthread.php?t=2327473 (download the latest v17)
3. .211 kernel and .96 kernel http://forum.xda-developers.com/showthread.php?t=2418991
4. flashtool
If you done preparing all the files, lets get it started (with detail steps)
1. install sony pc companion http://www.sonymobile.com/my/tools/pc-companion/
2. After installing, plug in your phone, drivers should automatically install after that
3. Install the fastboot and flash mode drivers from the flashtool folder
4. After done all these steps, your device should be properly detected by your computer
The next part is flashing kernel(make sure sony pc companion is not running in background as it may interfere the flashing process)
1. extract both the kernel just now you downloaded to the firmware folder in flashtool
2. run the flashtool
3. click the thunder icon and choose flash mode
4. choose .211 kernel from the list and click flash (ignore the selections beside the list)
5. wait for awhile and a window should pop out to tell you plug in your device
6. now power off your phone, plug in your phone while pressing volume down button, release the button when green led appears
7. your device now will connect in flash mod and start flashing kernel
8. once it is done, it should tell you to reboot your device
9. now your device should running .211 kernel
Now you can root your device http://forum.xda-developers.com/showthread.php?t=2327473 steps are provided in the thread:laugh:
After rooting, you will see supersu or superuser in your apps drawer
Now you have successfully rooting, now what you do is revert the kernel back to .96, steps are same as above and make sure to choose .96 kernel in flashtool
Hope this will help you in your problem
New answer
PLEASE CHECK THE NEW INFORMATION IN THE FIRST POST BECAUSE I CAN'T PUT URLS HERE
I know the CAPS thing, i'm just saying because i don't want no one to miss the information, because i was able to root the phone in less than 5 minutes without flashing or anything!
hendrickson89 said:
PLEASE CHECK THE NEW INFORMATION IN THE FIRST POST BECAUSE I CAN'T PUT URLS HERE
I know the CAPS thing, i'm just saying because i don't want no one to miss the information, because i was able to root the phone in less than 5 minutes without flashing or anything!
Click to expand...
Click to collapse
Thx for sharing, i think this is same as this one http://forum.xda-developers.com/showthread.php?t=2453709 i no need to refer to the video because i can read chinese
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
get this: [Toolkit] Wug's Nexus Root Toolkit v2.02
It has a guide for the folder you have, under: Initial Setup > Full Driver Installation Guide... > Step 3 > Driver Solution # > Manual Configuration.
coolncool said:
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
Click to expand...
Click to collapse
...
You should be asking these questions on a Windows forum.
You need to right click Android 1.0 device... Update Driver (basically, tell Windows Device Manager that the driver for the "Android 1.0" device is in that folder you got there)... it will install it, and that part is done. Then reboot the device to fastboot mode and manually update the driver again (it will come up as a different, yet again unknown device, you just feed it the same driver again)
Also... for the operations you're mentioning... "root, unlock bootloader, install cwm, flash rom".... you probably won't even need ADB, just fastboot. As in, you don't need to root before all that. You root in the end. And most custom roms are already rooted too.
This is assuming there's an exploit out there that still allows for root to be achieved without unlocking the bootloader.
So this morning i thought it would be a great idea to revert back to stock.
i was following the KDZ lg flash tool however while it was flashing (got to about 2%) i stupidly knocked the phone and the usb cable came out....
so now when i turn my phone on it goes to a black screen with
Fastboot mode started
---reset---
---port charge--
i have tried going into download mode again but it still goes into this fastboot mode.
i found a lot of threads on this such as
http://forum.xda-developers.com/lg-g3/help/tutorial-fixing-fastboot-mode-started-t2995854
this got me to install adb/fastboot which i did via
http://forum.xda-developers.com/showthread.php?t=2588979
however when i try and run through fastboot it just comes up as waiting for device
i have attempted to install lg drivers for this but still nothing.
inside device manager it comes up as
other devices - android?
so clearly the computer is recongnising it, i just need a better driver.
I have the ldf ready to go, if only i could get it to recognise the fastboot command...
anyone able to help, i realise there is a lot of information on the web for this, after extensive research everyone seems to suddenly get into download mode each time. which is something i cannot go. and no recovery doesnt work either.
other things to note, just to save questions..
i am running LG D855 16gb.
when i attempt to go into recovery it comes up with the option to wipe device, but when i follow through menu comes back to fastboot mode started.
i attempted to install lg pc suite in hope that it would suddenly pick up the device and go through the fix upgrade errors (to no luck)
so to clarify, i cannot get into recovery, or download mode. my screen is sat on fastboot mode started.
i am running windows 8.1 although i have attempted to plug into a laptop with ubuntu but same story.
any suggestions? i have also seen a through about jtag...but i dont have any screwdrivers at this point so trying to avoid that.
thank you for reading, kind regards
Anyone out there that has any idea on how to fix?
im convinced i just need to turn the "other device - android" into something that can be recognised by adb, but other then the stock lg drivers i dont have anything else.
help?
FIXED - figured it out, i plugged it into ubuntu again and noticed that when it was connected it came up under fastboot with "accepting commands"
i then put my laf.img file into my home folder and
opened terminal
sudo su <enter>
fastboot boot laf.img
phone then went into download mode
as i didnt have any tools installed on ubuntu i then unplugged and plugged into my windows laptop and ran LG Flash tool 2014 and flashed my kdz.
hope this helps anyone who has the problem in future
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.