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

[SOLVED] Unable to back up NV Data on S3 i9305

I purchased an unlocked, unbranded i9305 S3 LTE and have not been able to back up the NV Data.
I tried this with it completely stock and even though I have tried both settings with DM in Qualcomm USB settings and the port is found in QPST it always says 'No Phone'.
After trying this on several computers, I then installed Clockwork Recovery Mod and Rooted the phone successfully, and still had no luck connecting with QPST with the same 'No phone' message.
I also tried using EFS Pro and the Qualcomm NV Tools, the phone says at first it is connected but the program freezes and then says the phone has disconnected. I tried unticking 'Read Phone version information' and it connects. But as soon as I try to read any data the Rx Tx indicators flash a couple of times in the app and then I get the same Phone disconnected message.
Can anyone help? I have searched here and online and found lots of similar cases but no solutions...
Thank you very much in advance.
Stock ROM 4.1.2
CWM 6.0.2.9
Baseband version I9305BVBLL2
Kernel Version 3.0.31-633241
Build Number: JZO54K.I9305XXBLL5
-------------- SOLUTION -------------------
I managed to work out the solution!
Dial *#9090# and ensure that you have DM/DUN over HSIC selected.
Phone rebooted and was found!

DaveWoolly said:
I purchased an unlocked, unbranded i9305 S3 LTE and have not been able to back up the NV Data.
I tried this with it completely stock and even though I have tried both settings with DM in Qualcomm USB settings and the port is found in QPST it always says 'No Phone'.
After trying this on several computers, I then installed Clockwork Recovery Mod and Rooted the phone successfully, and still had no luck connecting with QPST with the same 'No phone' message.
I also tried using EFS Pro and the Qualcomm NV Tools, the phone says at first it is connected but the program freezes and then says the phone has disconnected. I tried unticking 'Read Phone version information' and it connects. But as soon as I try to read any data the Rx Tx indicators flash a couple of times in the app and then I get the same Phone disconnected message.
Can anyone help? I have searched here and online and found lots of similar cases but no solutions...
Thank you very much in advance.
Stock ROM 4.1.2
CWM 6.0.2.9
Baseband version I9305BVBLL2
Kernel Version 3.0.31-633241
Build Number: JZO54K.I9305XXBLL5
Click to expand...
Click to collapse
I don't own this phone but are you sure you have a Qualcomm processor? From these 2 pages:
http://www.morecellphone.com/phones/samsung-galaxy-s-iii-gt-i9305/304
http://www.gsmarena.com/samsung_i9305_galaxy_s_iii-5001.php
it should have an exynos processor, so those qualcomm tools won't work. (think qualcomms are just some specific models)
Can't you just get into some custom recovery, adb to it from your computer (or terminal emulator) and 'dd' an image from the /efs partition out of it (needs root)?
How i did it:
Opened terminal emulator and typed "mount" to check my mounts. Looked up the one that had /efs on it. It should also say something like "/dev/block/mmcblk0p3" (this is the one on mine, use whatever you got from "mount"). Then do something like:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
where the "/sdcard" is the directory where you want your efs image to go. Then you just need to copy the efs.img file to a safe place and you're done.
If you need to recover just do the opposite
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
Careful with the "if" "of" order, and with what you type. dd is a powerful command and it's easy to screw up irreversibly if you overwrite a different partition by accident.
Another method, I've manually copied /efs file contents with root explorer to my sdcard and later to my computer and was able to use them to recover my phone (had an app wiping my /efs by accident).
This is how i did on mine and worked but i've heard those qualcomm's (if you really have one) have a different method and what i'm saying may simply not apply

Thank you for your response. Unfortunately even though it does not have a Qualcomm processor it does use this chipset for the modem I believe.
I've been following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=1946915 but not having any luck. The phone is fine but it is not recognised correctly in QPST or EFS Pro....

I managed to work out the solution!
Dial *#9090# and ensure that you have DM/DUN over HSIC selected.
Phone rebooted and was found!

[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] Can not ADB my device?!

I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.

By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.

The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back

Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.

If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.

priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?

I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.

So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!

the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?

priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.

By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!

IMEI and BaseBand Version Fix Works 100 %

Lately i've been watching people as well as myself screwing imei and not getting reception.
There are two cases possible
1> You screw only the IMEI
2>You screw the baseband version also ( which in some cases makes the mobile lag )
Lets start with fixing the baseband version nothing can be done with a simpler way you just have to flash the stock firmware again and the next time you boot the baseband version will appear.
Imei Fixing
Prerequisite
** Make sure you are using Stock rom and Locked Bootloader
1> Install PDA Net and CDC Drivers*
2> Install MauiMeta 3G Software*
3> Download MTK 6582 NVRAM Database* (The Chipset our phone is using )
After you are done doing all these things
1) Open MauiMeta App
2) Click on Action select open NVRAM DB, A popup will appear navigate to the database files downloaded and select the db files and select the files starting with APDB... and the next time BPLG...
3) Click on Option on App and select "Connect Smart Phone In Meta Mode "
4) Select USB COM as your host and click on Reconnect
5)After doing this switch off your phone and connect it if drivers are installed properly the phone will boot in meta mode and the window besides the USBCOM will be accessible click on IMEI Tool if NVRAM DB files are asked provide it
6) Write the IMEI from the Mobile Phones Box (Behind) in both the tabs and press Upload to flash
7) Restart Phone
Voilà IMEI Appears and you can now get Network Signal
AS THIS IS MY FIRST POST AND I HAVEN'T COMPLETED POSTING 10 TIMES IN OTHER THREADS I AM NOT ALLOWED TO SHARE LINKS FROM OTHER WEBSITE WHICH INCLUDE THE SOFTWARE DRIVERS AND NVRAM DATABASE FILE. YOU TOO CAN BE INTELLIGENT AND GOOGLE THEM.
PRESS THANKS IF HELPED!!