Database Info

[How to][GUIDE] Bypass and Disable Password on lockscreen

Hello, as the title states I have found a way to bypass the password with the pin, pattern, and password option on the lockscreen without doing a factory data reset. I have not tried face unlock, I will try it soon. I would first like to thank Kosborn for his p2p-adb which bothe helped and gave me the idea. His p2p-adb can be located here.​
I will also be adding this feature to Kosborn's p2p-adb soon as well.
Now to get down to it.
What you will need:
Phone with eithier 'USB Debugging" enabled or a Custom Recovery
ADB
A file editor (I use Notepad++)
Basic adb skills
*If you already have "USB Debugging enabled please skip to Step 5*​
Step 1)
If the phone does not have USB Debugging enabled you need to flash a custom recovery to the phone. I will not post a step to step guide to on how to flash a custom recovery, just google it.
Step 2)
When you have the custom recovery flashed to the phone boot into recovery mode and mount /system. In CWM it can be found under "Mounts and Storage"
Step 3)
When /system is mounted pull build.prop and open it with the file editor I mentioned above.
Code:
adb pull /system/build.prop
You will have to add one line into the build.prop file for adb to be enabled when you reboot the phone
Add the line below to the build.prop file.
Code:
persist.service.adb.enable=1
Save build.prop file.
Now we have to push the file back to the phone so
Code:
adb push build.prop /system/build.prop
adb shell chmod 0644 /system/build.prop
Step 4)
Reboot phone
Run command below and you should see you device attached, If not make sure you have the correct drivers installed.
Code:
adb devices
Step 5)
Using adb type the following commands
Code:
adb shell mv /data/system/gesture.key /data/system/gesture.key.bak
adb shell mv /data/system/password.key /data/system/password.key.bak
Step 6)
Reboot phone
You should now be able to unlock your phone without having any password. And more importantly with having all of your data on the phone still.
If you found this helpful please hit the thanks button.

RESERVED

So this will work on any device correct?
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
With either pin lock or pattern?

prairiedogn said:
So this will work on any device correct?
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
With either pin lock or pattern?
Click to expand...
Click to collapse
In theory yes. I can't be for sure. It won't hurt it

When I had to use I typed "adb shell rm /data/system/gesture.key", not "adb shell mv /data/system/gesture.key" and that worked well.

eduds said:
When I had to use I typed "adb shell rm /data/system/gesture.key", not "adb shell mv /data/system/gesture.key" and that worked well.
Click to expand...
Click to collapse
That will work as well the reason why I used adb shell mv /data/system/gesture.key is to keep the file there when i was testing just incase but it could be removed as well.

not trying to be too much of a smart-butt, but heres the full version to do it, what u did is the basic commands, but leaves an empty pin/pattern for ANY input will be correct, heres each command (new line=new command):
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update secure set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
update secure set value=0 where name='lockscreen.lockedoutpermanently';
.quit
busybox rm /data/system/gesture.key
busybox rm /data/system/cm-gesture.key
busybox rm /data/system/password.key
busybox rm /data/system/cm-password.key
busybox rm /data/system/locksettings.db
busybox rm /data/system/locksettings.db-wal
busybox rm /data/system/locksettings.db-shm
reboot
some kernels+file-systems(or user actions) convert databases to "wal", or "shm" so they will have different names, as for some newer CM-based rom builds, the pattern, gesture unlock (if implemented), and sometimes pin get put into a different file "cm-***.key" but pin+password goes into "cm-password.key";
u need to only do first two commands(adb shell, and the cd), then skip to after the .quit if u ARE NOT locked out, if u are u need to do ALL these commands, and if it says "file/directory not found" or simmalier errors when doing the "gesture.key","cm-gesture.key","cm-password.key", the "locksettings.db-wal" +"locksettings.db-wal"; just ignore those errors as u dont have the configurations stored in there like some other custom roms do =)
i found and compiled this list from my app i made, if u heard about it "SMS Tasks", and this is acually the exact code (in adb shell form, not in java command line with added characters, voids, etc...) to unlock the phone remotely =), idk why people tell me not to share this code, as its good for users to have so they dont lose their data incase of forgotten passwords on devices stored in their dressers/storages for ages and got out for whatever reason (maybee a new rom-tree was born for it and u want to see it in action, idk =S) but use this if u want, if not u can ignore this post, just wanted to share this with u incase u want to add some to the OP as the commands u do some roms might not fully unlock (it will erase pass/pin, but some roms keep the config that its still set, but any pass (even one characters+a single_space, or one-three dot patterns), so if anyone got those errors, or want more understanding on what files are used, this is my most resent list of things to delete by what i see used on rom developer's github's anyways =S
but hope this helps any of u in any ways =)

much simpler way
download aroma file manager from
http://forum.xda-developers.com/showthread.php?t=1646108
flash aroma file manager in cwm with system mounted
browse to data/system
delete gestures.key
delete password.key
restart
of course you will need aroma file manager on the root of your sd card so download it and put it there now for safe keeping
you can always put it there via a card reader or pop your sd card into another phone if your phone is already locked

Using Aroma File Manager would be the easiest way!
Thanks for the share Marcussmith2626!

There is a way to do this without USB Debugging enabled nor Custom Recovery installed, as long as stock Android system recovery <3e> "backup user data" option is working:
- create a backup
- modify the backup file
- root the phone
- restore backup
root is not required for backup, but for restore. i prefer restore from custom recovery. but i have done this without flashing, too.
please see this link
Android system recovery <3e> alternative restoring program

i know this is an old thread, but im trying to bypass the screen where it says that youve tried your pattern too many times on a zte z932l (also known as the rapido) for a friends sister. She really just wants the pictures that are stored on the internal memory is all because they are of her kids. Any ideas on how to get this done? I would up on this thread because i was hoping that usb debugging had been enabled, but it hasnt

no "backup user data" option in Android system recovery <3e> i guess? if you can't create a backup then my friend, this is the hardest case for unlocking... if playstore is working and wifi enabled, you can unlock using Android Device Manager first. if this not help, check if fastboot is working. you can boot custom recovery with "fastboot boot recovery.img" if no fastboot mode available, find any way to make a backup of usrdata partition (maybe in download mode?) once you have a backup, its easy to modify and restore (as long as FRP lock is disabled)

with usb debugging enabler you can modify a rom and flash it via odin (without losing data???), and with Android Multi Tools you can unlock the screen. if this is possible for samsung devices, then there should be a way for other phones, too. another way is to enable adb via sideload, if someone will create such app.
and of course, if fastboot mode is available, the easiest way is booting a custom recovery without flashing it. then just delete /data/system/locksettings.db* files from adb or with aroma file manager (try calung version 1.80)

[HOWTO][TUT] Unlocking SIM operator for Galaxy SL i9003 [GUIDE]

You want sell your phone and you need to unlock ?
You have change the sim card and facing with the unlock code ?
You bought it used phone and you just perceive that it is blocked by operator ?
You given your phone at friend and surprise the phone stuck saying code with other sim card ?
Here is the solution to your problem many website are there to unblock but it is not free!
This is your ideal place for your easy, effective and free unlocking
highly recommended
You can start by Uninstalling Samsung Kies who no longer useful !
How to FULL Clean i9003
- Install Driver Samsung and reboot your computer
Format your SDexternal with SDformter https://www.sdcard.org/downloads/formatter_4/
Full LF2 inclued (DRIVER SAMSUNG,ODIN 1.85,PIT,BOOTLOADER,PDA,PHONE,CSC,CF ROOT)
extract this in C:/
With Odin 1.85 only !!!
Mode DOWNLOAD (vol down + power + home) 5 seconds
PIT > latona_20110114.pit
BOOTLOADER > botloader
PDA > CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PHONE > MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC > GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
At bootanimation Samsung Reset on Odin
After first boot Power OFF
With Odin 1.85 only !!!
Mode DOWNLOAD (vol down + power + home) 5 seconds
- CF Root LF2 (PDA only with Odin)​
If you want to unlock your phone is now on STOCK SAMSUNG ONLY !!!
requirements:
- Install the Adb driver (see tutorial : install drivers ABD )
- Download and unzip unlock_i9003
- Have a Roote phone ( you have to do beforehand )
1.) Enable USB debugging in the settings of the Samsung Galaxy (Applications / Development)
2.) Connect your Samsung Galaxy
3.) On your computer launch unlock.bat contained in the unzipped folder.
4.) Wait unlocked . Your mobile will restart.
Check that your phone unlocked, enter the code on the telephone keypad 5) .
CODE:
*#7465625#
If Network Lock is off, your phone is unlocked
​​
enjoy...

LoLaTiOn said:
If Network Lock is off, your phone is unlocked
Click to expand...
Click to collapse
adb shell "mkdir /sdcard/efs_backup"
adb shell su -c "cp -d -r /efs /sdcard/efs_backup"
adb shell su -c "rm /efs/nv*"
adb shell su -c "rm /efs/.nv*"
adb push nv_data.bin /efs
adb shell su -c "chmod 755 /efs/nv_data.bin"
adb shell su -c "chown radio.radio /efs/nv_data.bin"
adb push nv_data.bin /efs
adb reboot
Click to expand...
Click to collapse
Please correct me if I understood it wrong, but what this actually does is install a previously unlocked file. Am I right? Would that mean all users that follow your methoud would end up sharing the same IMEI and losing their own?
Thanks.

jamartinezdlv said:
Please correct me if I understood it wrong, but what this actually does is install a previously unlocked file. Am I right? Would that mean all users that follow your methoud would end up sharing the same IMEI and losing their own?
Thanks.
Click to expand...
Click to collapse
Yes it would. In deed, I follow the steps, and network lock is off but IMEI was changed. So be carefull.

This way also help you to recover your original IMEI if you have lost yours after a rom installation from a zip file. Thanks a lot!

Clean install can restore your original IMEI, after that backup your IMEI than do this method, if your IMEI changed, you can restore it from your backup...CMIIW...

can i start the second method (root , adb , and run the batch ) without the (first step ) odin step ? i am running the official firmware , hoping for a fast reply , thanks :good:

yes

LoLaTiOn said:
yes
Click to expand...
Click to collapse
thanks dude for ur reply , another question and the last one
my friend has the same device but when he dials *#06# it shows IMEI: (empty) and his phone is SIM locked when he inserts any sim card it asks for unlock code, do u think this method will solve this problem and unlock the phone ?
thanks again :good:

will this method work if there is no IMEI ???

i think yes but no add IMEI you can try > [I9003_EFS_ODIN_BLANK_TEMPLATE.tar] flash odin
source by dhuru1602
http://forum.xda-developers.com/showthread.php?t=2329937

I did this method, but lost imei and signal
recovery imei from backup, and lost unlock

no signal

Guys, may I know please how can I unlock my phone using the advice given here, which is the extra file that needs to be flashed, is it PIT or PHONE or CSC ? I have a different phone, but I think it works similarly.
I already installed Cyanogenmod and it was still network locked, and if I install a branded ROM from another country I guess it will be locked again. Now downloading a custom ROM, but I don't know what will be the outcome, but maybe I could add an extra thing to flash to make it unlocked.

[MOD] [root] [CHUWI] [Vi7]

This is a guide on rooting the new Chuwi Vi7 Phablet as a result of spending lots of hours on this proyect with the hope that others find it useful.
This is work in progress, do not attempt it if you are not ready to flash back the original rom in case you soft brick your Chuwi
PREREQUISITES:
A) For LINUX users:generally install the android-tools package so you have the adb command available.
In Manjaro linux and Arch Linux just do
Code:
sudo pacman -Sy android-tools
In Ubuntu probably
Code:
apt-get update && apt-get install android-tools
A) windows users would need to (presumibly; not tested)
For WINDOWS users:
install the intel drivers for android and user the attached adb.exe with dm-verity support
Most ADB.EXE do not have dm-verity. Try installing Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file reported to work fine is android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
1) (Recommended) Apply the over the air update; you know you have it when you can see the Google Playstore installed.
2) Connect your Chuwi Vi7 to your PC with a microusb cable
First we need the ability to write to the system partition so in order to do this, run these commands:
Code:
adb root
adb disable-verity
adb reboot
wait 30 seconds now we are going to do a backup of SYSTEM and DATA just in case
(if you are in Windows remove the ./ before system_068 and data_069)
This will take some minutes
Code:
adb boot recovery
Wait a few seconds until you are in the stock recovery
Code:
adb root
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 ./system_068
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 ./data_069
adb reboot
3) unzip the attached file and transfer all the individual files contained to the Chuwi´s /data/local/tmp folder
Code:
adb root
# Now we are going to push the whole folder contained in the archive we just extracted
adb push RootChuwiVi7 /data/local/tmp/
4) Now from a terminal run this command:
Code:
adb shell /system/bin/sh -x /data/local/tmp/vi7root
alternatively run
Code:
./rootnow
and that´s it!
Now open Root Verifier (it´s an app) to check if your Chuwi is rooted...
If you like my work dont forget to press the THANKS button and/or donate
TIPS: If you do not get prompted to allow root access by superSU, do adb root from the command line
If you need to flash the phablet here you can download the rom and flashing tool:
https://mega.nz/#!QVFCGDCa!oz4jXrxdsE6pJ4rVt4AlbUHN-VY9NwTF7SNfeir0mSk
Password: jopasaps
You need to install the intel drivers and the flash drivers and run Flash E2, load all the rom files, click on custom order, tick all the boxes, select generic usb, click on NEXT, turn off the phablet, then click on USB1 and very very quickly plug the phablet to your PC while holding VOLUME- you will see some activity in the screen and within 1 minute it will be ready.
If it is ready within 5 seconds then you did not load all the files. Depending on why your phablet is soft bricked it may be enough to flash only some of the files.
KNOWN ISSUES: Open Source superuser by koush does not work as the su binary needs recompiling. We are therefore using SuperSU by chain, I suggest you don't update SuperSU in the Play Store.
TROUBLESHOOTING: the command adb reboot ptest_clear is reported to work with soft bricked devices (put here as a courtesy, not needed in principle)
UPDATE: Download this file to update your SYSTEM partition to the latest version of the firmware, including some debloating and with English as default language. This update is done from recovery, through an adb push command

Thanks for this! I'm trying but can't get it to work. Running the script generates errors and I've boiled it down to doing the permissions -- I can't mount /system as RW no matter what syntax I've tried. I'm in the ADB shell and running under SU (#). Also tried mounting explicit as /dev/block/dm-0 but it still only comes back as "mount: Read-only file system".

Try again from the beginning, you will be able to mount read/write system now...
ALSO VERY IMPORTANT, download the new attachment and use instead ...

Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?

My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
TheAndroidGeek said:
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
Click to expand...
Click to collapse

casacristo said:
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
Click to expand...
Click to collapse
For WINDOWS users:
I had various flavors of ADB.EXE and none of them had the dm-verity. Finally installed Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file I used as android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
Now rooted... but not sure what to do with this very low spec tablet I have so many other tablets (Onda, Teclast, Acer, etc).
Thanks casacristo!

Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file

@jasonx3
try this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
it is a full rom with root and gapps, with a script that flashes it (provided
you have a root shell)
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?

Hello Yuweng, good to see you, yes it has been a while... I don´t change hardware very frequently nowadays and not always I feel I can make a substantial contribution to the community
I have not used FlsTool but I have something to offer you....
Download this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
It is a complete dd copy of my system partition with a script that will verify the md5sum is correct and flash it.
I think this should work fine if you can be root though a recovery.
This system image has already root, busybox, google updates integrated
yuweng said:
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
Click to expand...
Click to collapse

Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...

Thanks! and by all means let us know if you succeed...
yuweng said:
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Click to expand...
Click to collapse

casacristo said:
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Click to expand...
Click to collapse
I did everything from your tutorial. Root checker says that root is present. BUT! I cant do opearations with system partiotion. I tried to: 1)adb root 2)adb remount. After that in command promt I see that remount succeeded. Root checker say that root is present... But I still cant do anything. System partiotion cant be r/w
Edit: Sorry, but I thing that it is a problem of some apps that are not ready for android 5.1.x

Is there original rom available anywhere with tools to flash it? (got my vi7 in a state where it show only first "chuwi" logo, no "intel" logo - just black screen (but PC for example sees ADB interface; unfortunately "no permission"). I'm hoping that's only software problem.
Edit: CRANE_EVB firmware (seems to be some vi7 compatible device, not vi7 itself) finally worked. Required that I force (in devices manager) "intel usb driver for android devices" to be used for my detected chuwi vi7 "adb interface", then "adb.exe reboot ptest_clear" and it starts, no more black screen, no more "PTEST VER 1.41" problem etc.
Anyway still looking for original vi7 rom (not that crane_evb thing).

Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Updates - 01-Sept-2015
Huge Thanks to best98 for carrying out numerous of tests... :good:
Conclusion : No point to further develop custom recoveries, after unlocking bootloader, vi7 will refuse to boot unless you press Vol+ for 3 seconds then only it will boot up normally, no one would wanna do that...
{
"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"
}
best98 said:
Hi
So, I tried to flash stock 3e recovery..
Code:
"Warning: Chip mismatch. HW is [Sofia_3G_R] SW expects [Sofia_3G]
Device synchronized.
Using: Faster CRC, Writing all blocks , Skip data CRC , Skip protocol CRC
Start downloading item 'CUST:recovery.fls'' from file 'C:\Android\Chuwi_V7\stock-3e-recovery.fls''.
Checksum OK (0x0000)
Process time was 656 msec.
Total time was 1359 msec.
Channel 1 is succesfully closed."
Still boots with the green/red/black screen..
Did the fastboot eom lock
Code:
PS C:\> fastboot oem lock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.506s]
finished. total time: 11.511s
Now, got the bootloop.. -> flashing the whole firmware : boots ok.
adb reboot fastboot
fastboot oem unlock
Code:
PS C:\> fastboot oem unlock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.299s]
finished. total time: 11.300s
Black/green/red screen..
fastboot format cache + fastboot format data = same Black/green/red screen..
I hit 'Vol+' it goes forward.. shows Intel logo and boots..
Pierrick
Click to expand...
Click to collapse

fastboot oem unlock confirm
gets
< waiting for device >
and nothing else happens
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse

Is it possible to overclock this device? 900mhz.... it sucks.

Hmm.. I could try.. nothing to loose, but can't get the communication to work.
I unlocked the bootloader throug the Developer Option menu. Is it enough ?
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse

Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...

Hi
Not changing the bootloader butusing a mix of the OP script and Chinese tablet -Intel Root- script worked.
One of the big deal was to have the ADB compatibility with "disable-verity" which is the last release.
Now, I will try to focus on TWRP.. but FLS with COM to USB mapping makes it a little bit complicated !
Pierrick

OK.. just tried this, and now, I have a green screen ..
Rolling back the 3e recovery worked but the result is still showing me, black/green and red lines.
Right now, tablet does not boot anymore, except those lines in green/black and red.. where no text is written - looks like locked inl in fastboot.
Willing to hear from you to get back the control of the tablet
Here are the settings I used - thumbnail !
BTW - attaching adb.exe that handles the disable-verity
yuweng said:
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Click to expand...
Click to collapse

SIM & Network Solution | Alternatively Downgrading

This guide was originally written by chief_os from 4PDA.ru on how to roll back to Oreo, but my network issues wasn't caused by downgrading and still this helped me out so big thanks to the guy from the beautiful Lviv.
I alter this guide a bit, according to what I've done to get my network to work.
Download all the given files:
Qualcomm Tool QPST_2.7.453.zip - unpack and install
QualcommIMEIRebuilder.zip (given in this thread)
daisyQCN.zip (given in this thread) - it contains the file daisy.QCN, which you will need to recover your IMEIs
Fastboot ROM image of your choice from here
TWRP Recovery twrp-3.2.3-0-daisy.img - move it to your ADB & Fastboot folder
Follow the steps:
Remove all your SIM cards from the tray followed by disabling PIN security
Make a screenshot of your IMEI numbers and store it outside the phone
Install QPST_2.7.453.0
Enable USB debugging
Unlock the bootloader with
Code:
fastboot oem unlock
and, if you don't want to lose your data, use the instructions with Vol- button given here.
Reboot with
Code:
fastboot reboot
Go to the dialer and open the diagnostic COM port by typing: * # * # 7 1 7 7 1 7 # * # *
If the code doesn't give you any feedback, type:
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
Disconnect and connect the cable, then check the Device Manager for a device qualcomm hs-usb qdloader 9092 (COM[port number]). If the device is not there - reconnect again.
Open QFIL.exe and check what port is your phone on. If you can't see any, click on SelectPort and choose your [port number].
Choose Tools, then QCN Backup Restore
Check Enable Multi-SIM, click Backup QCN and wait for the completion of the current backup (if something goes wrong, you can roll back)
The backup file will be in the given folder
Run Qualcomm IMEI Rebuilder and select downloaded daisyQCN.qcn file
Replace IMEI numbers with your IMEIs and click Rebuild
Run QPST.exe. Choose Restore tab, select the rebuilded .qcn file and click Restore
At this point you might want to check if all is working as it should. If not, proceed:
Create a backup of the EFS partitions:
Reboot in Fastboot by:
Code:
adb reboot bootloader
Boot into TWRP by:
Code:
fastboot boot twrp-3.2.3-0-daisy.img
and after requesting the password, do not press anything on the phone
On the PC, type the commands in the given order:
Code:
adb shell
mkdir -p / sdcard / Backup
dd if = / dev / block / mmcblk0p39 of = / sdcard / Backup / fsg.bin
dd if = / dev / block / mmcblk0p40 of = / sdcard / Backup / modemst1.bin
dd if = / dev / block / mmcblk0p41 of = / sdcard / Backup / modemst2.bin
dd if = / dev / block / mmcblk0p42 of = / sdcard / Backup / bk5.bin
dd if = / dev / block / mmcblk0p49 of = / sdcard / Backup / persist.img
dd if = / dev / block / mmcblk0p50 ​​of = / sdcard / Backup / persistbak.img
exit
adb pull /sdcard/Backup/fsg.bin fsg.bin
adb pull /sdcard/Backup/modemst1.bin modemst1.bin
adb pull /sdcard/Backup/modemst2.bin modemst2.bin
adb pull /sdcard/Backup/bk5.bin bk5.bin
adb pull /sdcard/Backup/persist.img persist.img
adb pull /sdcard/Backup/persistbak.img persistbak.img
Click the recovery button when requesting a password, go to Reboot and select System
Check if your backup files are in the ADB & Fastboot folder
Reboot the phone in fastboot and type:
Code:
fastboot oem edl
Flash the ROM via the MiFlash utility or via command line flash_all.bat batch file (don't choose flash_all_and_lock!)
Reboot the phone, go through initial setup and check if your SIM cards are working. If not, repeat steps 7 - 12
Check Enable Multi-SIM, click Browse and select the rebuilded .qcn file. Press the Restore button
When done, reboot into fastboot by:
Code:
adb reboot bootloader
Repeat steps 18 - 19
Run the following commands in turn:
Code:
adb shell
dd if=/dev/zero of=/dev/block/mmcblk0p40
dd if=/dev/zero of=/dev/block/mmcblk0p41
exit
Repeat step 21 and boot the OS
Now everything should work just fine.
In case of anything goes wrong, you can restore your backup .qcn file via QFIL (12 - 13) and then reflash your backups
Load into TWRP and execute commands:
Code:
adb shell
dd if = / dev / zero of = / dev / block / mmcblk0p39
dd if = / dev / zero of = / dev / block / mmcblk0p40
dd if = / dev / zero of = / dev / block / mmcblk0p41
dd if = / dev / zero of = / dev / block / mmcblk0p42
dd if = / dev / zero of = / dev / block / mmcblk0p49
dd if = / dev / zero of = / dev / block / mmcblk0p50
exit
fastboot flash fsg fsg.bin
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
fastboot flash bk5 bk5.bin
fastboot flash persist.img
fastboot flash persistbak persistbak.img
Reboot.
In some rare cases you may still experiencing network problems. If so, check your EFS partition if it doesn't contain some weird looking folders. If yes - just delete them. [need to edit this part later].

im stuck at step 9. my device doesnt show up on QFIL.

Did you install drivers? Qualcomm & official from Google.

Quick downgrade to Oreo guide:
Backup your data to Google Drive
Remove SIM tray
Go to Settings -> About Phone -> tap Build Number numerous times til it says you have Developer Options
Enable OEM Unlock & USB Debugging
Turn the phone off and turn it back on in Fastboot mode (Vol- + Power buttons)
Type:
Code:
fastboot devices
fastboot oem unlock
It will erase all your data. You might want to go with Vol- trick if you want to preserve them
Go through the initial setup just to enable Developer Options and USB Debugging again
Turn the phone off and turn it back on in Fastboot mode (Vol- + Power buttons)
Type:
Code:
fastboot devices
fastboot oem edl
The phone will go blank but it'll be still visible under COM in MiFlash, don't disconnect your phone, just click refresh
Unpack the ROM image of your choice twice (you have to get to the unpack point where there will be a folder with files in it)
Choose the correct path in MiFlash
By default, MiFlash is set to clean all and lock (flash_all_lock.bat) and while it's EDL process, it doesn't really matter, what option you choose
Flashing will take some time (around 10 min), just go and enjoy a nice cup of tea
When MiFlash says SUCCESS, disconnect the phone and turn it on by pressing Power button (hold it for about 15 sec)
Go through the initial setup and check your connectivity on both SIM cards. They may be swapped, so just look it up how to fix it (step 29), but if the connectivity is good and you don't mind, just leave it
If you choose to leave your bootloader unlocked, just setup your phone
If you want to lock it, restart again in Fastboot mode and type
Code:
fastboot devices
fastboot oem lock
And again: it will erase all your data. You might want to go with Vol- trick if you want to preserve them

Sometimes, at the first boot, when it asks you to insert your SIM cards, it doesn't read them correctly. Just leave the tray with SIMs inserted and restart the phone.

Oh, and if you don't want updates, just turn Automatic System Updates off in Developer options.

Qpst software is not installing
I've tried with different versions but reaults are the dame...it says installation incimplete due to an error....what to do niw bro. ?!?

Unknown baseband xiaomi a2 lite android 8.1
{
"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"
}

As posted in my own topic where you replied: https://forum.xda-developers.com/showpost.php?p=80681201&postcount=9
Your manual needs some work though.
QPST is not needed, only QFIL should be enough.
Latest QFI: https://androidmtk.com/download-qual...ge-loader-qfil
Enable Multi-SIM is not in all versions. I've used v2.0.1.9
Restoring QCN with this version can take a while. DO NOT USE PC until done!
8. daisy_sprout:/ $ su
/system/bin/sh: su: not found
127|daisy_sprout:/ $ setprop sys.usb.config rndis,diag,adb
setprop: failed to set property 'sys.usb.config' to 'rndis,diag,adb'
16. is not "QPST.exe" but "QFIL.exe"
20. 21. 22. not needed. directly went to 23 from 19.
stopped at 27, rebooted phone, IMEI's are back. Did not proceed with the manual any further.

Man! You are awesome! Thank you! I've fixed my phone with this metod! I hope it will help a lot of users

For anyone still watching this thread, I have some questions and tips. I followed this guide once and I recommend downgrading to the first version of Oreo, then flashing the new QCN file with your IMEI numbers. After that you should probably backup your modem/persist partitions with TWRP. Ok, question time. I seem to lose my IMEI after wiping modemst1 and modemst2. Is this normal or not? Is there anything I can do to fix it aside from restoring a backup? And also, what would happen to my IMEI and data if I were to restore the modemst1 and modemst2 files from the download? I presume those are a backup of someone's own IMEI, as is the QCN.

Hello guys.
I am in trouble about Mi a2 lite.
Mi a2 lite not start after flashing and continue running start screen .
I run this command without backup and flash the software.
Code:
adb shell
dd if = / dev / zero of = / dev / block / mmcblk0p39
dd if = / dev / zero of = / dev / block / mmcblk0p40
dd if = / dev / zero of = / dev / block / mmcblk0p41
dd if = / dev / zero of = / dev / block / mmcblk0p42
dd if = / dev / zero of = / dev / block / mmcblk0p49
dd if = / dev / zero of = / dev / block / mmcblk0p50
exit.
Please help me if any one know in this regard.
[email protected]
Sorry for my English..

Awesome solution that solved my network issues after downgrading from Pie to Oreo.
It's not really clear in the guide, I did all the steps 1 to 15 while my I was under Pie and then executed step 16 (restoring .qcn file) after flashing Oreo.

ADB change bluetooth_name not working

Hello,
I am working on a script to provision many android tablets using adb via usb.
The devices all have root access and android 8.1.0.
Some settings I need can be changed using the settings stored in /data/system/users/0/settings_global.xml
i.e.
Code:
adb shell settings put global bluetooth_on 1
However changing the "device name" which is the bluetooth_name stored in /data/system/users/0/settings_secure.xml does not work.
This is the line:
<setting id="218" name="bluetooth_name" value="tablet-99" package="android" defaultValue="tablet-99" defaultSysSet="true" />
Code:
adb shell settings put secure bluetooth_name "tablet-77"
--> this just changes the value and not the defaultValue (how to do this?) ... both settings are reset after reboot
--> changing the file manually via sed/vi is reset after boot
In this thread Cloning Pre-configured Android 8.1 Device / ROM changing settings_secure.xml settings seems to work without problems.
Where else could the setting be stored?
thanks and peace.