Database Develop

Has anyone tried this free sofware SIM unlock?

http://forum.gsmhosting.com/vbb/f606/acer-liquide-unlock-solution-100-working-1092894/
I am confused because the OS update from the global Acer site doesn't create a folder called "qcn" or "01" or "03."
If anyone knows how to get this free unlock working, please educate us. I'd rather not pay for an unlock.

I did not try, but I downloaded the file, and translated the french, not sure what to make of it, I think it could be dangerous if it's for liquid and not liquid e, although, writing nv items on most similar devices should be the same
French to English translation
Flasher / unlocked his Liquid AMSS in Fashion
Render unto Caesar what belong to Caesar:
I would like to thank DNA without him if he was not mistaken in the keys that I have given him, I'd still be looking!
Right now the heart of the matter ...
The Acer software to reverse mode AMSS Tools uses to flash the baseband before flashing the rest of the liquid, you could just put up this system, those with Maleza recovery or at worst by fastboot.
But in any case we could touch the baseband, much less dream of désimlockage its Liquid!
The method I'll suggest is as dangerous as a flash! In fact it is one! So be very careful, no hurry, because even if it is recovered through this method, about 10 minutes of flash is a long time anyway!
With this, any liquid is recovered even those whose method fastboot can not walk alone are not such that the light at all, unfortunately, more vibration and hopelessly lost!
If you still have access to your phone, do a backup!
Otherwise:
0 Download this-> http://www.mcboydesign.fr/media/acer_liquid/amss_mode/amss_mode.zip and unzip it!
1 Turn off your phone if it is not already the case!
IMPORTANT: The drive must be disconnected!
Volume 2 Make (and not-as Volume Recovery!) Picture Power, all at the same time, the liquid will vibrate twice, but nothing appears on the screen!
3 Plug the USB into Liquid on your phone, I do not explain here how to ask the drivers, there is enough explanation on the Forum!
If you're curious, you'll see in your device manager in "port COM & LTP" a port whose name appeared is quite explicit!
4 Open Acer Tool!
IMPORTANT: If you're running Vista and Seven, do not forget to right click on the icon of acer tools and do "Run as administrator", if not crash!
5 You will see that you are logged in AMMS (connected (AMSS)), with "Browse" go get your bin, select "Select QCN File Manually" and START!
6 A window appeared, press "Yes"
7 And there does not touch anything, the flash is short, about 10 minutes or more depending on the PC!
...
8 A window is opened again, select the file I give you (desimlock.xml) And be open,,,
9 Do not worry your Flash will be a long shot, as if he walked over, wait (almost a minute!)
10 Do not touch anything now as you do not "Process Finished, You Can remove USB" Acer Tools!
11 Enjoy! Finished!
This method replaces fastboot and serves also unlocked
Small Tip: In another flash, Acer Tools has detected a former NAQ, and my re-simlocker Liquid, Think A1_QCN delete the directory at the root of C: (or save it elsewhere if you prefer!)
I hope this will help everyone!!
Remains for me to figure out how to manually send files to other AMSS and not having to use Acer Tools!

dan-htc-touch said:
I did not try, but I downloaded the file, and translated the french, not sure what to make of it, I think it could be dangerous if it's for liquid and not liquid e, although, writing nv items on most similar devices should be the same
French to English translation
Flasher / unlocked his Liquid AMSS in Fashion
Render unto Caesar what belong to Caesar:
I would like to thank DNA without him if he was not mistaken in the keys that I have given him, I'd still be looking!
Right now the heart of the matter ...
The Acer software to reverse mode AMSS Tools uses to flash the baseband before flashing the rest of the liquid, you could just put up this system, those with Maleza recovery or at worst by fastboot.
But in any case we could touch the baseband, much less dream of désimlockage its Liquid!
The method I'll suggest is as dangerous as a flash! In fact it is one! So be very careful, no hurry, because even if it is recovered through this method, about 10 minutes of flash is a long time anyway!
With this, any liquid is recovered even those whose method fastboot can not walk alone are not such that the light at all, unfortunately, more vibration and hopelessly lost!
If you still have access to your phone, do a backup!
Otherwise:
0 Download this-> http://www.mcboydesign.fr/media/acer_liquid/amss_mode/amss_mode.zip and unzip it!
1 Turn off your phone if it is not already the case!
IMPORTANT: The drive must be disconnected!
Volume 2 Make (and not-as Volume Recovery!) Picture Power, all at the same time, the liquid will vibrate twice, but nothing appears on the screen!
3 Plug the USB into Liquid on your phone, I do not explain here how to ask the drivers, there is enough explanation on the Forum!
If you're curious, you'll see in your device manager in "port COM & LTP" a port whose name appeared is quite explicit!
4 Open Acer Tool!
IMPORTANT: If you're running Vista and Seven, do not forget to right click on the icon of acer tools and do "Run as administrator", if not crash!
5 You will see that you are logged in AMMS (connected (AMSS)), with "Browse" go get your bin, select "Select QCN File Manually" and START!
6 A window appeared, press "Yes"
7 And there does not touch anything, the flash is short, about 10 minutes or more depending on the PC!
...
8 A window is opened again, select the file I give you (desimlock.xml) And be open,,,
9 Do not worry your Flash will be a long shot, as if he walked over, wait (almost a minute!)
10 Do not touch anything now as you do not "Process Finished, You Can remove USB" Acer Tools!
11 Enjoy! Finished!
This method replaces fastboot and serves also unlocked
Small Tip: In another flash, Acer Tools has detected a former NAQ, and my re-simlocker Liquid, Think A1_QCN delete the directory at the root of C: (or save it elsewhere if you prefer!)
I hope this will help everyone!!
Remains for me to figure out how to manually send files to other AMSS and not having to use Acer Tools!
Click to expand...
Click to collapse
i tried ur method bro, but when i choice desimlock.xml file, Acer tool show Sever connection fail, and phone stuck at recovery mode...plz help bro

[Q] S3 LTE I9305 - Unable to boot, corrupt OS? and data recovery

Hi all,
I hope you can help as something very strange and unusual has happened to my Galaxy S3 LTE i9305 (on Orange in UK). Samsung technical support tell me they've not heard of the issue before as do the official repair shop. I have never installed any unusual software or tried to access the internals etc.
On Sat 26th Oct, in the evening, the phone was connected via USB to my laptop charging. There was no data transfer taking place, and the laptop was idle. The phone was not in use, nor was I nearby but randomly it showed the Samsung splash screen logo - it looked a little weird as it was pure black but with random speckles of coloured dots (which made it look like a Galaxy - I thought perhaps I hadn't noticed it before). I was unable to reset so took the battery out and replaced. It did the same thing and then on the second time of removing hte battery the screen became completely white with black marks generating a fuzzy effect - it's been like this ever since.
I get the white fuzzy screen if attempting to turn the phone on, or attempting to recovery mode, however if going to the install option (which I assume happens before Android boots), the screen is absolutely fine and proves not to be at fault. I should add the screen is cracked slightly, it has been since April and is not the cause of this random error.
Tech support tell me that they'll happily accept it back but ultimately, they will wipe the phone and send back as reconditioned. I've tried to connect via Kies, device not found - nor is it when connected to a computer - infact the computer tries to 'install device drivers'.
I'm sure everyone says this however I am an organiser of a large local festival in the UK and the phone has some very important detail storesd in the ColourNote app which I need to access - also the contacts appear not to have synced with GMail since May.... I'm desperate to access these files, for money too potentially, but cannot afford to go down the simple, wipe and reformat easy option. Can you help? Do you know any software that can access data from the internal memory card (note I've removed the external card which contained the photos) How about once the phone has been wiped, to try and see if anything can be recovered then.
Would really appreciate your support, this developer community is my last option and you're normally so awesome, as can't find any reference to the problem online.

Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .

JJEgan said:
Is your colour note app not synced ??
You can try RECUVA data recover.
You need to read the faqs and guides first .
Including the one that covers storage and recovery ..
Samsung reject warranty on phones that have damaged screen .
Click to expand...
Click to collapse
Hi,
....no I had never set it up. So ironic that was on the to do list in the app.
I'll look into Recuva, is that for before or after I send it off. Is there much chance do you think?
Yes, sorry. I meant to say I also have phone insurance which covers the screen so will have it off to them first, and then onto Samsung - ie 2 places of data wiping!
Thanks for your reply though,
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely

s_boddy said:
Kind of hoping I may just be able to fix the problem, even if only temporary, but realise it's unlikely
Click to expand...
Click to collapse
Hi mate,
You can try flashing just the system (and boot) images if you think it's a software issue.
That way your data partition will be intact.
Instructions:
Step 1) Download the Stock ROM you want to use
Step 2) Rename the file from .tar.md5 to just .tar
Step 3) Open the .tar with WinRAR or something similar
Step 4) Extract: system.img (and boot.img if you want the Kernel)
Step 5) Create ODIN file from .img files http://forum.xda-developers.com/showthread.php?t=1484304
Step 6) Flash the new ODIN file to restore your firmware to Stock!
On Windows you can use Cygwin to run these commands if you don't have access to Linux.
NOTE 1: That guide uses recovery.img as an example but you can replace that text with system.img on the first line.
NOTE 2: If you are adding more than one file (eg. system.img & boot.img) simply list them one after the other with a space between each file.
NOTE 3: Do not include data.img, it WILL wipe your data! Do not include cache.img, hidden.img, these MAY wipe your data!
Best of luck, I hope this helps you out :fingers-crossed:
Have a great day!
-Shaz

So, here’s how you can recover data from a Soft-Bricked Android smartphone:
1. Once you’ve installed a custom recovery on your device, open it using the specific method for your device. E.g for Samsung you can turn off the device completely, then turn it on by pressing and holding Volume Up + Home + Power Key and you will be able to access the recovery. These methods vary for different devices.
2. Once in CWM or TWRP Recovery you will find a number of options.
For CWM Recovery, select “Mounts & Storage > Yes”.
In Mounts and Storage menu you will find some more options, from the list select “Mount USB Storage or the option depending upon your choice.”.
Now connect your phone to your PC using the data cable.
As soon as you connect your phone to your PC, the USB Storage / Internal Storage will open up in folder view.
You can copy all of your files to your PC now.
3. For TWRP Recovery, Select “Mount > USB Storage”.
Connect your phone to your PC and it will open up the USB / Internal Storage.
3. Copy your desired files.
That’s all! You can easily recovery all of your data stored on the internal storage of your Android device.

[Q] No Option to Update

Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!

Well, I guess I stumped everyone in here as well. I just sent the device back to Asus for the second time in 2 weeks. Let's see if they do anything more than just power on the device, deem it "working properly" and promptly send it back to me.

Shaundiesel said:
Hello,
I've already sent my device back to Asus, where they did absolutely nothing and just sent it right back to me. Complete waste of $16 shipping.
anyway, a while back I received a notification to update firmware. It downloaded, but then the install failed. About 2 weeks later, it prompted me again, and once again it downloaded but then failed to install on the restart. I decided to download the latest firmware on the Asus website, but I have no option to install by SD Card once I'm in Droidboot. My only options are:
1. REBOOT
2. REBOOT DROIDBOOT
3. RECOVERY
4. POWER OFF
Can someone please help? Asus has been absolutely no help, as I just spent another hour yesterday "chatting" with the rep who knew absolutely nothing!
Thanks in advance, cheers!
Click to expand...
Click to collapse
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.

WeAreNotAlone said:
I have (2) K01A MemoPad 170CX's, less than 30-days old. Both updated to 4.4.2 via OTA method running software Image Version: V11.2.3.27. (2014-12-23)
On one all of the sudden (and it may be a case the camera never worked) is when the camera is activated the cam app comes up for (3) seconds with the still icon lit up, then the video icon lights up as well for a (1) second then app exits to desktop with a "No Camera is found" error message.
I've been all over the net trying to find into on how to manually flash it.
According to the very cryptic info on ASUS website step # states:
"2. Download device software and Update SOP (From “Manual” Item)"
Googling for info on SOP, you download firmware in zip format, then do (1) extraction of the contents to a MicroSD card formated FAT32 to the root of the card. (After extraction there is a zip file named ifwi.zip that contains (4) *.bin files that remain inside the zip, you don't extract that zip.)
According to info on SOP, with device powered fully up inserting the sd card is supposed to bring up a prompt, a icon on the taskbar/, you click the prompt and the update process begins.
I'm not seeing that.
All I see when the SD card is inserted is a notification the SD is being prepared for use.
When trying to update via DROIDBOOT (W Fastboot wording at bottom of screen), with SD card inserted the DROIDBOOT menu isn't coming up, when I fire up DROIDBOOT without the SD card inserted and insert it DROIDBOOT does not recognize any change has occurred.
Wanted to try re-flashing WW_V11.2.3.27 as I've read in cases the camera gets the No camera found error message the camera firmware gets corrupted somehow. when you hit the return to home-screen icon too fast, I guess when app is in process of opening and it's closed before it initializes fully.
If that doesn't work, trying Version WW_V11.2.3.28 as I for sure don't want to have to send the device back to ASUS when a simple reflash of the firmware would get the camera working again.
Q: Are / were you getting the same results?
(I guess you didn't try SOP method?)
Q: I guess "Fastboot" means "neutered"? Is there a way to bypass? /enable all functions ASUS would not be able to detect if I have to send in unit for service?
Tried copying the contents of the removable SD card to the internal SD card folder...
Nada, zip, nothing.
ASUS needs to provide info on how to run the flash, I've never had this much trouble flashing a device.
Click to expand...
Click to collapse
I tried everything under the sun....I extracted the zip, nothing. I left it as a zip, nothing. I went to recovery, nothing. You name it, I did it. So, I sent back to Asus for the second time in 2 weeks. I just checked the status of my RMA with Asus, and it states that "No trouble found." I'm not sure how NO TROUBLE IS FOUND when I can't even update to Asus latest firmware for their device? In addition, I do not get the options to try to manually update (Not that I should even have to go that route when it should be OTA). I will never own another Asus product. I've only had my tablet for 4 months, 2 1/2 months of which it sat in my desk, unused. Asus is garbage.

Did you remove any system files or freeze them? Did you root?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
No I did not remove any system files or freeze them, that I know of. I rooted shortly after purchasing this, but unrooted the device about 2 weeks later.
Thoughts?

lvnatic said:
Did you remove any system files or freeze them? Did you root?
Click to expand...
Click to collapse
If you are talking to me in which camera(s) both seem to not be found by the OS ME170 is STOCK, STOCK, STOCK.
Contacted the vendor TigerDirect, noticed that they claim they will NOT do exchanges due to "manufacturers polices". While I realize it costs vendor (TigerDirect) to handle exchanges that wording could also indicate they have run the numbers and don't want to be bothered.
Reading about ASUS service, and my interaction with ASUS when I contacted them does not insipre incidence so I'm hoping to be able to flash the device and cameras will start functioning again.
In regards to the customer being able to flash a device (Which I done numerous times on other brands)
I know ASUS is a Asian based manufacturer and sells worldwide but they really need to have persons who can write in better ENGLISH.. ASUS needs to publish detailed instructions on how to flash device, additionally they need to update support pages with any drivers, tools to do so vs just posting the firmware with vaque reference to SOP.
Q: How long after firmware updates appears on ASUS site does OTA update get pushed?
..

Just an update....
Just received my memo pad back, and it appears to be finally fixed. It took sending it back twice, and escalating to a supervisor, but it looks good now. I've actually received 3 firmware updates in 2 days, so it was REALLY behind! What firmware are you all running right now? I have WW-3.2.23.201.

I think 201 is the latest. Mine is still on 199 though and it won't try to update again since it failed a couple of weeks ago.

can anyone offer me some help

Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated

Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.

but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this

BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.

thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks

Bluetooth issue after reboot

Hi there,
last morning my G Watch R rebooted and after that there was some kind of bootloop, the Google animation started and after some time just stopped and the watch rebooted. I put it in Fastboot mode and charged it for some time, then i picked it up and noticed it already rebooted and this time it was working... But now I have the Problem that bluetooth is not workng anymore, in System Settings it shows the device name without the 4 numerical characters just as 'G Watch R'... After enabling developer mode and starting an ADB shell I did a 'logcat' and there seems to be an issue with the file '/data/misc/bluedroid/bt_config.conf, which can't be accessed to start the bluetooth stack. So I installed TWRP on the watch and went to the mentioned path just to see there is no single file in there... I looked on my phone in the same path and there are 3 files, 1. bt_config.conf, 2. bt_config.bak and 3. bt_fw_version.txt. Does anyone know how I could restore those files, I already tried flashing the latest firmware but I guess those files are not included in the updates because they contain data like MAC Address and so on. May be someone can take a look at his files on the watch and post them here without data like MAC and so, so I can try to put them back to where they belong with my own data... I guess my flash somehow got corrupted and so the files are gone.
Druidster