Related
Let it now be hacked by the USA! France, those silly, um, baguette-eaters, via Bloggee, has several videos and some forums (in French) showing (but I don't think explaining) a hacked Archos 70B ereader/tablet. Can we get there??
I'd like to see a guide for hacking this 130 euro Android tablet!
About: I AM A N00B. I AM UNWORTHY! You are all wiser and cooler and better at all of this than me. I cannot write code, except some CSS and HTML, blah blah beginner stuff. I was the guy that jailbroke friends' iPhones when we studied in Italy. I like learning how to do things, but can't get extremely in depth, though I respect the process and the art behind it. Currently, my iPhone died so for a phone I have a quad-band Huawei J2SE POS I couldn't modify much, and a netbook with dual-boot Win7/Linux. Now in Germany, I bought a lovely Archos 70B ereader, and while it does the job of ereader, it's ugly and clunky and I want to hack it into running a cleaner, prettier Android ROM (with marketplace) since this seems to be a new device with a lot of potential.
Questions that haven't been answered by looking through these forums, and that I have encountered trying to customize my tablet:
Trying to get marketplace, I finally found an .apk to download, but trying to install, it said (paraphrase) "Only works with Froyo." SOO, Android's various versions (Eclair, Froyo, Gingerbread, Honeycomb, etc) while all the same OS in a way, prevent apps compatible with one version from being installed onto another version. It's like trying to install Win95 stuff on XP, or Win7 stuff on XP. Correct?
Issue: Finding Eclair-compatible .apk files. Where are they? Or, can Eclair apps be installed on other builds of Android, & vice versa?
Trying to upgrade the hardware to Froyo, well, I can't find anything. If a machine has the minimum hardware specs, why is installing any version an issue? Why can't I just search certain websites for an installer package and then use it, like a Windows or Linux .ISO, etc?
Issue: Upgrading from one Android OS/version to another (Eclair to Froyo, Froyo to Gingerbread, Eclair to Gingerbread)
Trying to upgrade firmware on device, I've found that Archos' website has no downloads for 70B ereader...HMMM. Issue, much? My firmware on the device is 1.0.1. There is no "Update Firmware" option or anything, and the firmware display is grayed out, so you can't touch it for further details or anything.
Issue: How do I update/backup/recover firmware for this device (or any, I guess)
While I have found guides to using Nandroid to backup a system in case of issues, they all seem to require that you have Marketplace so you can get Nandroid...and since this Archos version of Android doesn't have Marketplace...I've tried AppBrain Appmarket but the webpage isn't helpful: it says dl nandroid from marketplace or navigate there on my device's browser, but my device's browser won't download the APK when I visit the site. How does one get nandroid and a solid backup without marketplace? (.apk anywhere??)
Permanent rooting on this device; currently I use Z4Root and do temporary rooting, since 1) that's what guides said worked and 2) I don't know if permanently rooting my device will somehow destroy my data or be unrecoverable without further restore options.
Issue: Permanent root vs. temporary root (and why use one or the other)
Installing a custom ROM. In short, because I just am not clear, can someone clarify for me? Is this like basically wiping the HDD to all 0's, down to the first sector, and installing an entire new OS (called a "ROM") onto the HDD? I know a flash HDD is different than a circular spinning drive with Windows and an MBR, etc, but I'm curious if a custom ROM erases EVERYTHING, including a flash drive equivalent to all recovery/installer partitions. Or is there a tiny partition left and, if the factory reset button is pushed, that reinstalls/recovers everything? If that is not the case, then don't I need stock Archos ROM to reinstall/recover, if I wanted to go back to that?
Issue: Does a custom ROM completely wipe a HDD all to 0's, and if so, how does recovery work if using a device-specific build for Android (like Archos')
Maybe nobody cares about this tablet, and sure it's slow, but having a sub-$200 Android tablet would rock, and figuring out how to root and ROM and customize a device would be great.
Also, I want to say that most important is knowing if/how/why I can return to my stock Archos version of Android if dissatisfied; second most importantly is how to improve this (and any) device with a crappy tweaked Android OS into a pretty and fast (with marketplace) Android OS.
THANKS
Current for Archos 70B
Model Number A7EB
Firmware Version 1.0.1
Kernel Version 2.6.25 [email protected] #14
Build Number v.0.18.ECLAIR.eng.root.20110324.142810
Have successfully rooted (temporarily, until reboot) via Z4root.
Currently trying to use ArcTools...I had the site linked, and lots of other nifty links throughout, but xda handicaps us n00bs until 8 posts. So no links. Sorry.
Currently...
stuck at the same place as these people, pretty much.
http
forum.archosfans.com
viewtopic.php?f=82&t=51066
sorry for breaking it up. insert slashes to go to the link, or just visit the forum and search for Archos 70b.
currently looking into loading the (much nicer-looking) Voltaire firmware onto the 70b, if the parts are the same...hope i don't get a spanish installer program
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
IMPORTANT QUESTION !!
Can i downgrade when i do this ^^ ?
i have found this:
xxx:xxx.archoslounge.net/forum/showthread.php?t=17642&p=275535&viewfull=1#post275535
^^
firmware_Archos70bereader.zip
xxxx:xxx.multiupload.com/U8MOUTWI5T
Does not work
It crashes at 99%. Luckily I had a recovery image.
I followed all the steps but can't get the image to install properly
We really need a rooted version of the BQ Voltaire software. Mine has now crashed twice since using it. If I could backup it wouldnt be nearly so bad.
The temporary root doesnt seem to work for me.
I have recently brought the Archos 70B ereader. I would like to know how to perform a factory restore. I have already tried to the reset button on the back, but that's just resulting in turning of the device. I also noticed the startup wizard on the setting menu, which after adjusting the startup setting is adding the factory apps back to the device. However, it does not seem to erase the whole internal memory like a real factory restore would do.
Does anyone knows how to perform a real hardreset on the reader?
Thanx.
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
I have a bq Voltaire running latest firmware (1.0.8) an i was able to temp root with Universal Androot.
will try to perm root and report back
...but is there any rom with software buttons (back, home, menu)?
because the bq does not have them...
cheers
EDIT: was unable to perm root with either Universal Androot or z4root...
I also have the software installed BQ. Works perfectly. I can not say that the batterylif is a problem. BQ software works much better tehn de the Archos Software.
The Archos 70 b eReaders and BQ Voltaire tablet run with the firmware Voltaire_20110699_v2.0.9.-2 _update.img very stable. For some days has been there one for this equipment android 2.2 version. There were some crahs on my device with that and moving the Apps on a SD card also doesn't work.
A rooted version with containedly in the Link2SD (you can move the Apps on SD card) the above-mentioned version in the link. E.g. an optimal mode of operation is possible with a 32 GB SD card class 10.
The Mini tool partition software can with standalone the SD card be formatted into 2 partitions. 1st partition FAT32 (e.g. 28 GB) 2nd partition ext3 (rest) both primary.
The approx. 2 GB suffice for many Apps.
For link see Archosfans forum. (i can't write link here)
Works like a charm with the Voltaire rom!
So THANX guys
how to remove key locks ?
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Hallo all and thank you for this great manual.
I allready prepared all: downloads, installing usb and uncompressing and so on, tryed many times, but my problem is your point 7): remove key-locks. , whichj I didn´read clearly before and thats why I want to install any new system on my/our Archos BQVoltaire: My daughter played with the login until it was locked and I do not have any Google-Password to unlock this. Nor dont know, how to hard reset or anything else. I am just a user, nothing else. Tried everything, but didn´t get it.
Do anybody hav an idea, how I can solve this, I would be really happy. Thx a lot in advance.
Giant THANKS, is easy as instruction say, and works a charm...now i have a tablet instead of a****!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Point 7) of the instruction ????
Maybe for you woks like a charm. :good: Congratulations, fine for you.
But my problem has not been solved, since july last year!! I understand the entire instruction, already downloaded all indicated files, but as I already mentioned, my problem is point 7 of the instructions: "7. remove locks on keys and install the new device using uncompressed drivers"
.
The thread here is called something like "how to hakk keylocked installation...". Isn´t it?
But in Point 7) says: ".. remove locks on keys..." !!! What a fool is this, it is ridiculous. If I could remove this f... keylock manually, so why should I make a hard-reset.??? This is the REASON for what I´m going to do this !!!
My Archos ereader is not stolen nor part of any fraud. It just were handled foolish form my daughter, which is 10 y old.
Ok, if anybody have another idea, how to remove this keylock, you are welcome, thx
cvesch said:
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
Click to expand...
Click to collapse
For me it was the same. The drivers are working only on 32-bit win WinToUSB - cool tool, if you don't want to reinstall your win.
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.
Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-
Hello my name is Sean and I have recently rooted my phone (captivate glide) and installed a custom ROM. Whenever I try to update apps like the AT&T Code Scanner, Qik Video Lite, Andoid Keyboard, or even Google Play itself I receive this error message:
"Package file was not signed correctly. Uninstall the previous copy of the app and try again."
Also when I run certain apps like Spot Hero or Clash of Clans I get the following message:
"Google Play services, which some of your applications rely on, is not supported by your device. Please contact the manufacturer for assistance."
I have searched the forums and found a few instances with similar problems, but the issue was either never resolved or didn't match the problem I was experiencing. I've Googled the problem and a few folks suggested using Titanium Back Up to uninstall the app in question and then re-install, but I have read some users say that they are then unable to re-install the app. I don't want to lose any functionality, so I haven't tried that.
Here is a step-by-step of what I did to my phone:
1) Shutdown my phone and rebooted into download mode with Odin 3.04 running
2) Flash CLOCKWORK MOD RECOVERY 6.0.1.2 (found here)
3) Reboot in download mode
4) Flash stock ICS ROM (found here)
5) Flash Superuser 3.2-RC3-arm-signed.zip (following the instructions found here)
5) Flash GApps.zip for 4.0.4 (found here)
6) Reboot and the phone says it's upgrading Android and optimizing applications
7) Once the phone is booted up and the SD card is done scanning I run into the problem described above
Has anyone encountered this problem before? If so, please share your insights.
Thanks for reading and if you have any suggestions I would welcome the help.
hello
i remember i had same problem when i was using ics, i think you shoulr flash anotherics gapps from diferent source. I do not remember where i downloaded mine
I tried some different gapps and I got some apps like Hangouts to update, but now I receive this message when I try to install Google Play Services:
"Incompatible with other application(s) using the same shared user ID."
I did some further looking into this and found that if I wiped my /system data and reflashed my gapps.zipp that seems to work. I installed Youtube first (since it requires Google Play Services) and that took care of everything.
Unfortunately I have lost any progress I may have made in my game apps and have to download/update everything from scratch and reset my ring tones and such, but at least I have a fully functional, rooted phone.
Actually I take that back. Google Play Services seems to be cooperating, but now I'm getting the package file signature problem again.
I resolved the issue by starting over and following Rawr0w0's guide half way down this thread.
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.
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(