Related
Hello there,
I am new to this forum and android as well.
I have xolo play cell phone which is recently being useless because of too many times pattern attempts.
I know email and password but which is not useful as my internet connection is disable.
I also activated xolo secure due to that i am unable factory reset in recovery ( it says first you'll have to unlocked xolo secure but phone is locked) .
I also disable the usb debugging because i use many time to take data or download using cellphone...PC.
BUT
But the thing which i came across is i boot phone in "factory test" mode due to that i think my usb debugging on for that time i am able to view directory in phone by cmd (adb) and able to reboot using command prompt:.
Now you guys work on android from so much long time is any one know command from which i can factory reset my phone
I dont want to take my cell to customer care because i rooted my phone.
Lastly if no option i have to go customer care support.
dhakeparag81 said:
Hello there,
I am new to this forum and android as well.
I have xolo play cell phone which is recently being useless because of too many times pattern attempts.
I know email and password but which is not useful as my internet connection is disable.
I also activated xolo secure due to that i am unable factory reset in recovery ( it says first you'll have to unlocked xolo secure but phone is locked) .
I also disable the usb debugging because i use many time to take data or download using cellphone...PC.
BUT
But the thing which i came across is i boot phone in "factory test" mode due to that i think my usb debugging on for that time i am able to view directory in phone by cmd (adb) and able to reboot using command prompt:.
Now you guys work on android from so much long time is any one know command from which i can factory reset my phone
I dont want to take my cell to customer care because i rooted my phone.
Lastly if no option i have to go customer care support.
Click to expand...
Click to collapse
http://www.sendspace.com/file/t5cw1x
Instructions for upgrading the software.
1. Please copy the software in sdcard
2. Ensure the name of the folder is us9230.v2
3. Press power key and center of volume up & Down key at the same time
4. A message saying " Updating ... Pleaes do not press any keys " will appear
5. Please be patient till the update gets complete, approx takes around 5 min.
6. Phone will get shut down automatically.
NOTE:
unzip the file and copy contents to sd card... all contents should be in the folder named 'us9230.v2'
dhakeparag81 said:
Hello there,
I am new to this forum and android as well.
I have xolo play cell phone which is recently being useless because of too many times pattern attempts.
I know email and password but which is not useful as my internet connection is disable.
I also activated xolo secure due to that i am unable factory reset in recovery ( it says first you'll have to unlocked xolo secure but phone is locked) .
I also disable the usb debugging because i use many time to take data or download using cellphone...PC.
BUT
But the thing which i came across is i boot phone in "factory test" mode due to that i think my usb debugging on for that time i am able to view directory in phone by cmd (adb) and able to reboot using command prompt:.
Now you guys work on android from so much long time is any one know command from which i can factory reset my phone
I dont want to take my cell to customer care because i rooted my phone.
Lastly if no option i have to go customer care support.
Click to expand...
Click to collapse
Dear Member...
here is the solution to wipe in fatboot mode...
connect phone to pc in fastboot by pressing Volume+ & Power...
enter the following command to communicate with phone....
1. fastboot -i 0x0955 reboot-bootloader
2. fastboot -i 0x0955 -w
3. fastboot -i 0x0955 reboot
That's all....:fingers-crossed:
How did you open dat factory test mode... i cant get to open dat... and did u solve ur problem...I m da same trouble...
Thank you man but facing a new problem
jaspuneet;48743356
Instructions for upgrading the software.
1. Please copy the software in sdcard
2. Ensure the name of the folder is us9230.v2
3. Press power key and center of volume up & Down key at the same time
4. A message saying " Updating ... Pleaes do not press any keys " will appear
5. Please be patient till the update gets complete said:
Hi,
XDAForums has saved my life before as well. Thank you for posting this solution. This works and phone has been factory reset and unlocked, however it doesn't say SD card data will be wiped out. My SD card now doesn't show any files or app. Phone detects SD, but no files and can't detect any apps. However SD card is not empty. I am not much of a technical guy, is there any way to reinstate apps from SD card?
Thank you in advance.
Regards
Click to expand...
Click to collapse
how to unlock xolo q500 while in pattern lock
i am also same problem
but my phone is xolo q500 help me to out of it
I'm using xolo q1100 i try to recover my xolo secure password but it failed. Can this app helpful?
Sent from my Q1100 using XDA Free mobile app
how to enter in full item test or manual item test in xolo play 8x 1020 help me plz
Hello everybody !
Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :
I explain everything with details to not waste your time when you will help me !
When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.
At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.
So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success
At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...
I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !
P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...
Many thanks for your help, and thank you for reading everything !!
Max
Up !
BackDraft647 said:
Up !
Click to expand...
Click to collapse
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
[email protected] said:
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
Click to expand...
Click to collapse
You're such a genius ! I will try this evening ! Thanks a lot !
Didn't do anything. It's not working. I was thinking my wifi was just broken, but something creepy happened this morning. The Wi-Fi worked again (I downloaded one thing to be sure !) and then... My phone froze, and reboot... Is the devil inside my phone ??
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM : http://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
BackDraft647 said:
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM :
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
Click to expand...
Click to collapse
can you tell me what firmware you used exactly? because i tried to flash the first one, from the asus page.
But it says that i have a newest build and it doesn`t lets me past trough the installing part.
I am also having troubles with my wifi and i would like to fix it
Hello ! I don't remember exactly, I went on a website and selected the right version for my country ! But my problem wasn't solve at all actually... I brought my phone to the store, and they told me my motherboard was just burnt. They changed everything, and now it works like a charm ! Be careful with the custom kernel, I'm pretty sure that's how my phone broke (I'm very careful with batteries,...etc)
Well thanks anyway. I will try to take the phone to te oficial ASUS services from my country but i don´t think they give a new one. I live in Uruguay and this cellphone is not at sale over here
Does sideloading the firmware wipe your apps? Or is every thing still there when its done?
Sent from my ASUS_Z00AD using Tapatalk
Hello....I bricked my I927 when I accidently formatted my efs partition when using EFS professional .....my phone boots in download mode.....but only boots till samsung logo screen.....I tried various things like installing stock GB and ICS through odin and installing custom firmware but phone boots onle till samsung logo and then lights up with sone stange colored thin lines and screen goes off.....In TRWP I get a "unable to mount preload" error whenever I try to install somethiing.....I suspect that the EFS partiton is corrupted and needs to be repartioned....I had backupped the efs folder when my phone was working before.....its in a tar format.....I read somwhere that someone made a recovery.zip out of his backedup EFS.IMG and flashed it with CWM solved his problems which were exactly similar to mine.....can somebody on the forum make a recovery.zip for I927 with update binary and script so that I can add the backedup EFS image to it and flash it with CWM? Please.....this would also help many others who are facing similar issues.....and also what do I do regarding the "unable to mount preload" error? I need to repartition and tried to install hemdall.....but get the common .dll error even after following all the instructions and installing C++ 2010.....
Hi, k one thing after the other.
Do you have repartitioned anything?
Do you have adb in place and does adb works when in TWRP?
The easiest thing would be to connect by adb then mount /efs and then restore the efs backup. The good is that you will have a good chance to recover your device. Maybe you need to reformat /efs but that depends.
Which timezone do you live? Maybe a Teamviewer session would be helpful?
.
Thank you for your reply sir...
THANKS FOR THE REPLY SIR....YES I WAS ABLE TO GO INTO CWM RECOVERY AND CONNECT THE PHONE WITH MINIMAL ADB FASTBOOT.....AND AFTER SPENDING ALMOST 2 DAYS CONTINUOUSLY TRYING TO FIND THE PROBLEM USING GOOGLE, I TRIED DIFFERENT COMMANDS ON ADB TO GET EFS BACK OJ THE PHONE....BUT WITH NO SUCCESS...... MY EFS BACKUP IS IN TAR FORMAT......IT WAS MADE USING GALAXYSIMUNLOCK BY SPOCKY.....I LATER TYPED IN 'ADB MESG'.....OR SOMETHING SIMILAR TO THAT COMMAND, AND FOUND OUT THAT ALL THE PARTITIONS ON mmcblk0 were mangled up with strange letters.....for eg, p1, p2, p3 and so on had strange characters written next to them.....SO I TRIED TO RE-PARTITION THE WHOLE THING WITH SDPARTED......AND IT RE-PARTIONED THE SYSTEM (AROUND 7000MB).....MMCBLK01 (AROUND 500MB).....AND ANOTHER THING I CANT REMEMBER NOW.....BUT WHEN IT FINISHED THE JOB, IT GAVE ME A mmcblk02 ERROR.....AND WHEN WHEN I CHECKED MY PHONE ON CWM SCREEN, IT GAVE ME A LIST OF CACHE ERRORS.....AND WHEN I SWITCHED OFF THE PHONE AFTER THAT IT REFUSED TO POWER ON.....IT WAS NOT EVEN GOING INTO DOWNLOAD OR RECOVERY MODE.....BATTERY HAD ENOUGH POWER....SO ITS NOT BATTERY FAULT......I SUPPOSE THAT SINCE THE PARTITIONS WERE FORMATTED THE PHONE BECAME COMPLETELY DEAD......CAN YOU TELL ME IF THERE IS ANY WAY WHERE I COULD GET THE COMPUTER TO RECOGNIZE MY PHONE USING A 'DEAD PHONE USB FLASH' OR SOMETHING.....AND THEN FLASH A BLANK BOOTLOADER AND THEN WRITE CWM?
I LIVE IN INDIA SIR.....+5.30 GMT.....I DO NOT KNOW ANYTHING ABOUT TEAMVIEWER.....IS IT AN ANDROID APP? CAN YOU EXPLAIN MORE IN DETAIL SIR?
PLEASE LET ME KNOW HOW TO GET THE COMPUTER TO RECOGNIZE THE PHONE AGAIN......
Well.. that sounds not that good...
Teamviewer (www.teamviewer.com) is an easy to use and free remote control software for your PC (it runs on both Linux and Windows). We could do a remote control session if you like. I can try to help but cannot promise anything.
I live in Germany: GMT +1. Send me a PM if you want to give that a try. Next Monday. Tuesday or Thursday would be possible on my site. At least for getting a short overview.
.
Thank you sir,
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Ok I have made one. It want to say it was VERY hard to find the correct instructions to do so and therefore I'm absolutely not sure if that will work for you!
Test it if you like but again: I have no idea if that would damage anything more than it is now!
See --> http://forum.xda-developers.com/cap...od-unbrick-debrick-hard-bricked-i927-t3285505
If it worked for you (would be like a miracle) then please report back!
If it does NOT work for you please report back, too!
thanks
xdajog
.
UPDATE:
Besides the link I posted --> Could you please also try the following:
1) Power on your device and directly after that:
2) Press and hold down Vol Up + Vol Down (both the same time)
3) You should see a warning message like the attached one which is the APX mode
4) you need to release the vol buttons immediately after you see the APX mode otherwise it will continue to the non working download mode.
Does teamviewer require internet connection with a lot of data?
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Uhm do you have read my above post??
.
1927 wouldn't boot.....Help.
Ohhhh Thank you.....thank you.....thank you for your kind reply Sir.....how good of you to take all your precious time to help me.....I greatly appreciate all your hard work Sir.....wonderful...*.I wanted to download your img file to try it out and when I read the reply of brother Bubor, that the I927 woudnt boot from the SD card when the bootloader is bricked, I was very disappointed. Like I said before, I have a very very slow internet connection with very less data left....and according to brother bubor's reply I doubt this will work....It looked like he was sure that it wont work....I tried to get into APX mode as the link that brother bubor posted had mentioned, but no luck, as the phone is not going into APX mode.....I remember that when I was trying to get to the APX mode the first time, the computer flashed a notification that the APX driver was not successfully installed.....but after that I tried the method more than a dozen times, but the computer was not recognizing the phone to go into APX mode.....Does the phone go into APX mode when the full internal phone system is formatted? I tried your second method on trying to get to APX mode, but nothing happens.....the computer is not recognizing the phone.....The battery had about 30% power in it when the phone got bricked 2 weeks ago.....Dont know if the battery drained all these days of not using the phone.....And even if I get to the APX mode, I have no idea how to proceed from there to repartition the internal phone system and get back download mode.....In the link that brother bubor posted the person who made the thread has made some files to be used when one gets into APX mode.....The PIT and emmc files which are necessary for repartitioning the system and getting the bootloader work are found in that zip file.....But that zip file is for the I9103 Galaxy R.....there isnt something like that available for the I927 yet.....And is brother bubor sure that the unbrick.img file wont work on the I927?
Give it a try with my unbrick image.
we all don't know.
.
xdajog said:
Give it a try with my unbrick image.
we all don't know.
.
Click to expand...
Click to collapse
Hi @alvcross: any update on this?
have you tried the SD card unbrick?
You said you cannot open the APX mode but what happens when you press the buttons for accessing the APX mode?
Try it even if you see a blank screen and then connect your Cappy with USB to your computer --> you should get a message about a missing driver or similar.
If that works I tell you how to proceed.
xdajog said:
hi @alvcross: Any update on this?
Have you tried the sd card unbrick?
You said you cannot open the apx mode but what happens when you press the buttons for accessing the apx mode?
Try it even if you see a blank screen and then connect your cappy with usb to your computer --> you should get a message about a missing driver or similar.
If that works i tell you how to proceed.
Click to expand...
Click to collapse
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
alvcross said:
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
Click to expand...
Click to collapse
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
alvcross said:
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
Click to expand...
Click to collapse
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes Sir....I understand....
alvcross said:
Yes Sir....I understand....
Click to expand...
Click to collapse
Ok could you please try these driver package here: http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Follow the instructions there for installing
The next step (if the driver would work for you) will be to flash a working PIT to your device to make sure you are using the correct partitions.
Afterwards we will flash the bootloader (may absolutely brick your device if not done correctly) and then --> if all goes fine --> you should be able to flash in download mode whatever you want to.
So it is still a long way to go and I need to check all the steps first before actually we can proceed.
That may take longer so do not expect that this will be something in the next days.. sorry.
Update:
If the above universal driver do NOT work for you: Test these one here View attachment apx_driver_samsung.zip
.
Thanks for the speedy reply Sir......Ill do as you said and let you know Sir......thank you.....thank you.....thank you Sir....
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
alvcross said:
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
Click to expand...
Click to collapse
nvidia apx isnt fastboot/adb device. You can found tool on nvidia site ( more info https://ac100.grandou.net/nvflash ), this tool can read and write whole flash.
Before you could use nvidia's tool, you must send an uniq blob to your phone. APX mode is useless without this blob.
This blob is uniq for every phone.
I only connect my ZE551ML to my Windows 7 x64 when I've got to do firmware updates or transfer music, and I haven't done either in a while.
On my "MTP USB Device" driver I'm now getting: This device cannot start. (Code 10)
The ASUS Android Composite ADB and PC Link Interface drivers are loaded and fine.
Things that I've tried:
- the Asus android drivers
- the Intel android drivers
- the universal ADB drivers.
- different USB cables
- different USB slots
The perplexing thing is that the image that allows you to install "ASUS ZenUI PC Suite" is available as a CD drive, "PC Link" works when mirroring my phone onto my computer and using ADB from a command prompt can see my device.
I don't know what I've installed between the last time it worked to now, and I'm at wit's end with what I can do.
Anyone have a suggestion at a possible next step?
Do you by any chance have Windows 7N (one without media player)?
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
chiudikas said:
Do you by any chance have Windows 7N (one without media player)?
Click to expand...
Click to collapse
No, I'm running Home Premium, and have both media player and media center.
timbernot said:
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
Click to expand...
Click to collapse
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
azthemansays said:
No, I'm running Home Premium, and have both media player and media center.
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
Click to expand...
Click to collapse
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
timbernot said:
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Click to expand...
Click to collapse
That's the issue, when I get to that point it only shows "Internal Storage." As an aside, my phone's bootloader is unlocked and it's rooted.
*EDIT* - When I get to the part where I choose the directory, the file manager comes up with the "Recent" page. if I press the menu button, I get the option to hide SD card and file size, but in the list to the left it only lists "Internal Storage"
timbernot said:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
Click to expand...
Click to collapse
I just removed all the drivers that I could tell were related and am about to reboot.
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
timbernot said:
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
Click to expand...
Click to collapse
Still run into the same issue after remounting. It lets me select my internal, but not my SD. I guess it'll have to do for the time being - use it to move from computer to internal, then move it from internal to external.
And Removing selective ones in USBdeview still gave me the same issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so I went ahead and uninstalled all the ones that were for the specific USB slot, and am about to reset. Fingers crossed...
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
timbernot said:
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
Click to expand...
Click to collapse
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
Have a read thru here to get general idea what needs doing
http://forum.xda-developers.com/zenfone2/help/how-recovery-t3514205
---------- Post added at 02:53 AM ---------- Previous post was at 02:44 AM ----------
azthemansays said:
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
Click to expand...
Click to collapse
keep cal.m
timbernot said:
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
keep cal.m
Click to expand...
Click to collapse
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
azthemansays said:
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
Click to expand...
Click to collapse
First - transfer your stuff to pc off internal thru sharelink
unroot , flash back stock recovery .194 - reboot to recovery , update over adb , adb sideload .196 stock firmware , which should be renamed to MOFD_SDUPDATE and put in your fastboot/adb folder previously
adb cmd >
adb sideload MOFD_SDUPDATE.zip
set up not connecting to wifi - skip everything you can-- factory reset .
Set up correctly this time . Run for 3 days without any modifications . Make sure everything is running correctly :good:
timbernot said:
First - transfer your stuff to pc off internal thru sharelink
Click to expand...
Click to collapse
Already running into issues with the first step. Share Link gets to about 100mb transferred, then my phone's screen blacks out and is non-responsive, though it shows touchscreen presses (I have that turned on in developer settings). The transfer hits around 200mb and then the transfer gets cancelled. It's also rebooted twice.
This is getting to ludicrous levels.
*EDIT* - I tried uninstalling all the USB controllers in Windows Device manager in case they were corrupted, but I'm still getting the same failure with the generic "MTP USB Device" being installed instead of the Asus one and still getting that yellow exclamation mark. When I try to update it to the Asus one, it fails and disappears when I unplug and replug the phone. This is maddening because it was working in October...
*EDIT 2* - I'm thinking of testing it on another windows installation... I've got some spare HD space that i could partition and install another copy of my Win 7 on to see if it's my Windows or phone that's corrupted. If it's not my phone, I'll be able to transfer everything out...
Hey some news , after reading what you are experiencing - I remembered i have another lappy with windows 10 on in bedroom wardrobe - Not been used for nearly a yr , fired it up with wifi off and both my drives are visible
So , mine IS either MTK driver conflict or a windows update or both
Whatever , i will update it today and test further.
This does`nt explain your sharelink probs tho, mine transferred 443mbs of CM14.1 in 3 mins just now with the same prob you have.
Use file manager instead to transfer to ext SD. Instead of sharelink
And go about sorting it out , with whats already mentioned and with the fresh copy of 7 - hopefully it is windows and not the phone you said you had probs with from new
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
azthemansays said:
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
Click to expand...
Click to collapse
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
timbernot said:
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
Click to expand...
Click to collapse
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
azthemansays said:
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
Click to expand...
Click to collapse
Lets just get you up and running stock for a few days -- No mods ok ?
I think its best we flash raw at bootloader state , refresh here i will add files to download ready and info how to:good:
Flashtools - http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar install and run as admin
Raw collection of and thanks go to Realyoti there - choose .196, bottom one last of the LP
https://yadi.sk/d/FijRoAVJtvRiG
Video
Ignore the first 2:17 mins - fast forward to 2:18 mins for flashtool flash and adding raw and general settings > choose wipe data to prevent any bugs from previous state
Note -- you just let it complete on its own , the video goes to show how to correct serial number , you dont need to -- once it starts flashing - let it finish
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
When up n running say a thank you to Realyoti here please
http://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
timbernot said:
Lets just get you up and running stock for a few days -- No mods ok ?
Click to expand...
Click to collapse
Haha, sorry for putting the cart before the donkey at the end there...
But I was asking if I need to remove any/all of these mods before flashing the raw file? And does the raw file also include the recovery partition? That's why I was asking where to flash "recovery.img" to go from TWRP to stock recovery...
Just 19% into transferring all my Titanium backups to Google Drive right now.
Phone M8 Europe, OS 6.12.401.4
problem:
phone is unaccessible - Error: com.android.systemui stopped working
This happens after he (is not sure tho...) had his phone updating. It was not reacting, so he restarted several times. Finaly he got "preparing apps" (not sure about the english term for it, its appears after you update before you) what amde he think there were an update.
Now after you start the phone the message "com.android.systemui stopped working" appears over the lockscreen. The lockscreen is still visible, clock shows and is not frozen also i can see the statusbar, Volume keys are working too. When i click ok on that message the lockscreen disappears, i sometimes get some screen flickering seeing a background picture (my friend does not know this). Touch inputs not accepted or nothing happens, same for volume keys but i can push power and choose to restart, airplane mode, shutdown and touch-choose this. If i understand that problem right, its related to the homescreen, so if i somehow can bypass this the apps and menus and stetting will work fine.
Now there can be 2 reasons for that. First something went wrong while updating and restarting and second a problem with the launcher (Smart Launcher) he installed on the phone because he had trouble accessing the statusbar.
Now i want to access the phone without factory reset because of all the important apps/data stored and not backed up...
I cannot access via adb - no device shown, i think because of usb debugging not enabled.
Delete the cache did not solve it. I cannot clear Dalvik, HTC Recovery does not show that option. Also installing TWRP is not possible because i cant unlock the phone.
When i install a stock rom its the same like factory reset, right?
HTC Sync Manager will not find the device either.
I am out of options, maybe you have some ideas? Is it possible to fix this without losing all the data? Are there other ways to access the phone like plug in a keyboard and use key combination to try to get into a menu?
maerzhase said:
I am out of options, maybe you have some ideas? Is it possible to fix this without losing all the data?
Click to expand...
Click to collapse
Probably not. If the OS is not accessible, and the phone was not previously bootloader unlocked & TWRP, there is no way to retrieve the data.
You can run the RUU, which will probably repair whatever is wrong with the OS. But the RUU will wipe all data on the phone.
Either follow the instructions here, to run the RUU by htc_fastboot: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Or if you have an SD card, it may be easier to rename the RUU zip to 0P6BIMG.zip , put it on the SD card, insert in phone. Then restart to bootloader, and it should auto detect the zip and install it.
---------- Post added at 09:45 AM ---------- Previous post was at 09:40 AM ----------
maerzhase said:
Also installing TWRP is not possible because i cant unlock the phone.
Click to expand...
Click to collapse
Don't know what you mean by "can't unlock the phone"
Does that mean you tried, but were not successful? If so, describe the exact steps you took, commands, and specific outputs, error messages, phone status that resulted, etc.
Probably bootloader unlock is perfectly possible, and you just aren't doing it 100% correct. Although the process to RUU is probably easier. Unless you also want to root, custom ROM, etc.
Also, unlocking the bootloader will wipe all data on the phone.
Thanks for your help redpoint73.
Apparently i did not properly read the "how to unlock/twrp", looks like i dont need to put the phone into usb debugging.... Nevertheless does the disclaimer on htcdev warn me about getting all user data deleted in the process :/
Biggest problem is to get the user data, but all solutions i found to get access to the phone involve clearing it. A factory reset will do the trick and she can use the phone again i guess, since the phone is not exactly bricked...more like softlocked. Everything seems to be running fine but the home/lock-screen. If that wont help i will run that RUU.
I will do some more research maybe i find some other solution to bypass it, if not i will we reset.
Also i dont understand how data can be so important that its a tragedy if its gone, but not important enough to backup. but thats not my problem.
maerzhase said:
Also i dont understand how data can be so important that its a tragedy if its gone, but not important enough to backup.
Click to expand...
Click to collapse
There is no such thing. If the data is important to you (your friend, etc.), back it up. It's that simple.
There is a variety of ways to backup, and a number of tools were preinstalled on the phone. So there was really no reason for your friend to not be backing up.
Searching for ways to retrieve the data after something goes wrong, is not good plan. The likely result is going to be regret. But I guess some folks need to learn the hard way!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
maerzhase said:
Apparently i did not properly read the "how to unlock/twrp", looks like i dont need to put the phone into usb debugging....
Click to expand...
Click to collapse
You don't need debugging for fastboot commands; you only need it for adb commands. While adb and fastboot are related, there are important differences. Fastboot (not adb) is what is needed to unlock the bootloader or RUU.
You were right, i was not able to save any data. The problem itself was solved with a reset - phone working again, top of the screen still not accessible, prob. broken.