Related
Hi,
My kids accidentally locked the phone with a password that he cannot recall after locking it.
Now the phone is password locked. Is there any way to unlock it? I was informed by Samsung Service Center that only way is to format the phone to factory default but all data will be lost which I have pictures in the phone which has not been back up.
Any suggestion to get the phone unlock?
Unlock your phone
You can do a factory reset in the recovery, trust me, your data like photos and musics ... (external and internal memory) won't be deleted but your apps will (data apps too like saves in the games). I hope that I helped you.
Bye
playnote said:
You can do a factory reset in the recovery, trust me, your data like photos and musics ... (external and internal memory) won't be deleted but your apps will (data apps too like saves in the games). I hope that I helped you.
Bye
Click to expand...
Click to collapse
Internal memory will be wiped completely (apps, their data, settings and all files on the internal storage). External storage (microSD) will not be touched.
I have no suggestion about the password though. I am not sure about password, but PIN security does have the option to unlock via Google account if certain wrong guessing threshold is reached.
Yes you can !
I already did it after i forgot my PIN on the Lockscreen. You just need to wipe the lockscreen-options .config file with adb
Try to google this keywords
If you have USB debugging enabled its possible yes
Hook up your phone to your computer, after you've downloaded and installed the "Samsung USB Drivers for Mobile Phones.exe". Download adb.exe and call it from your command prompt/console, like this:
Code:
cd c:\adb-fastboot
adb devices
If it shows a device with a long ID attached to it, you're in luck!
If you are rooted, you can bypass the screen lock.
If you are not rooted, you can still copy your photos.
To get the photos, use the "ls" command and "adb pull" to browse through your device and copy files and pictures back to your computer. Instructions for that
You can also use "adb backup" to retrieve all files, all app data, and even apks from the phone.
If you don't have the long ID, try rebooting to recovery mode and run "adb devices" again. Otherwise try another computer.
To bypass the lockscreen, use this command:
Code:
adb shell
rm /data/system/gesture.key
If you still can't get your computer to connect (USB Debugging disabled), you're still in luck if you have a Google account linked on the phone and an Internet connection. Download this Play app to your phone from a desktop to transfer your pictures to external storage. You'll need your notification drawer accessible I believe.
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
goalkeepr said:
Thanks and all credit to Nameless One for the heads-up!
As found here - run this adb command to get changes to survive a reboot:
Code:
adb shell reboot disemmcwp
It seems there's system write protection enabled. That command will disable it. I changed my DPI and emojis and can confirm that both changes stuck!
Click to expand...
Click to collapse
Nice find, I'll be adding this thread to my Guides / Info Thread....
Thank you dude
Cool Awsome!! Now my phone is working properly with ROOT.
Is this step still needed? Been following the links on DrakenFX's thread that lead me here.
Thanks guys. The dev is much appreciated as is the guide pulling everything together.
Barsky said:
Is this step still needed?
Click to expand...
Click to collapse
Whether it is done by a script (if so there should be clear indication that it does this so people know where they stand in the overall process) or by hand it still needs to be done, it is a completely separate issue from whether or not the boot-loader is unlocked or the phone rooted.
Already did it. :cyclops:
Is this only needed if your bootloader is locked but you still wanna root ?
Ugh, so this was the reason why I couldn't uninstall system apps even w/ a system app uninstaller....
So developer unfriendly :/
Haha needed to do this on the official root for EU as well.
Yay, thanks guys! got adaway running. Starting to feel like home again..now to backup it before I screw it up..
I'm not getting it to work on my Axon 7 rooted with terminal emulator
Sent from my ZTE A2017U using XDA-Developers mobile app
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
nickcaper said:
Tried using emulator. No go. Tried using adb shell. still no go...
Can one of you explain to me the exact method? Maybe im doing something wrong
Click to expand...
Click to collapse
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
xtermmin said:
Boot into A7, enable developer options and enable USB Debugging, connect to computer, accept the computer's debugging signature on your A7 (if you've never gotten a pop-up that you've had to accept, it's not connected properly), type in "adb devices" in a command prompt to make sure that the device is showing up, and if it is, issue the OP's command.
Click to expand...
Click to collapse
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all it does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
nickcaper said:
yes, tried that. phone rebooted and still.. cant delete/remove system apps... aggrivating. ill try again later.. im tired of messing with this nonsense...
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Tried it again, all ti does is reboot.. I open RU uninstaller Pro and its still saying the same thing. That permissions are not granted.
Click to expand...
Click to collapse
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
xtermmin said:
Open the SuperSU app and make sure that you gave RU uninstaller root permissions.
Click to expand...
Click to collapse
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
nickcaper said:
tried that yo... aint happnin....
any other ideas?
When I plug the phone into the laptop, the phone has a popup that sks me which mode I want to use the phone.
I choose Media device MTP. I also tried the mode called connect to PC software. Both times, the phone is recognized by ADB.
yet it will not fix the permissions
Click to expand...
Click to collapse
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
xtermmin said:
Go into the app's permissions list and make sure that the Storage permissions is allowed.
If that doesn't work, then try using a different app all together.
Click to expand...
Click to collapse
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
nickcaper said:
Doesnt work..
I am thinking the problem is that ZTE put a lock on system files so no one can delete them or modify them.
There is suppose to be some kind of way to turn that off but I cant seem to do it on my phone.
Click to expand...
Click to collapse
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
xtermmin said:
/system has write protection enabled by default, but the command in the OP disables it. After turning it off by running that command, I'm able to uninstall apps via Titanium Backup fine.
Click to expand...
Click to collapse
Can you tell me if your phone is rooted? what update version si your phone? Mine is 27.
Did you do this permission fix before or after root? did you use an emulator to do the fix or adb?
So here is my situation.... I have a damaged digitizer (the component which makes touch screen work) and Samsung have said they will repair it under warranty. I have not rooted or flashed anything to this phone yet as I always wait until the warranty expires for this exact reason.
However, the technician at Sammy have told me part of the repair process is to reset the phone so I need to do a backup. Great, lets install custom recovery and make a nandroid backup of the phone and also root to use titatnium as a backup backup. Oh wait, Sammy says thats voids the warranty!! Hmmmm, what other options do I have to backup.....
I was advised to use Samsung Smart Switch to create a backup and then restore that to the restored phone. But after using this app, it only backs up the APKs of all apps then the data of a select few apps. Well thats not a backup in my eyes! For example, I have an app with an 8MB APK. The data it uses is 150MB (no cache). The app states the backup of this app is 8MB. Anyone see the pattern??
So the reason I am here is to see if the XDA community can confirm what I believe to be my only option left.
I understand you can fastboot into a TWRP recovery which means that TWRP is not installed but is run like a Linux Live CD. I assume therefore this means I can create my full nandroid backup and restore this after my phone is reset. Am I correct in thinking this? Will having this temporary TWRP trip knox or anything else which will void my warranty? Is there an issue with DMVerity by attempting to run TWRP this way?
Lastly, I have been trying to work out if my phone has a locked bootloader but I am struggling to find out if it has or not. I have the SM-G935F variant on the Three network in the UK. I have restarted my phone in recovery mode and cannot see anything which would suggest a locked bootloader. Rebooting to the bootloader just starts my phone up as normal. Does anyone have a surefire way to check for a locked bootloader?
Hope someone can help!
Helium. Doesn't need root. Backs up save data of most apps. Works in conjunction with SmartSwitch. Let SmartSwitch backup the apks and all other settings. Let Helium do the 'data only' backup.
Sent from my Galaxy S7 Edge Duos via Tapatalk
chanchan05 said:
Helium. Doesn't need root. Backs up save data of most apps. Works in conjunction with SmartSwitch. Let SmartSwitch backup the apks and all other settings. Let Helium do the 'data only' backup.
Click to expand...
Click to collapse
Thanks for your reply. I have looked in to Helium but it does not work out of the box for me. I believe this is down to the RPi using ARM architecture and the included adb is compiled for x86 / x64.
Luckily this isnt my first time with adb so I already have it installed for the RPi. So taking the script run.sh and reading in to it, I will run the commands manually and see if I can work around the included adb instead.
I will definitely be looking at koush's github to see what this com.koushikdutta.shellproxy.ShellRunner2 app is but he has a hell of alot of repos to look through!
I will update when I have more.
Well thats a fail!
Here is my update to the script to use the adb I have on my RPi (adb installed using apt-get install android-tools-adb):
Code:
pkg=$(adb shell pm path com.koushikdutta.backup)
pkg=$(echo $pkg | cut -d : -f 2 | sed s/\\r//g)
echo $pkg
adb shell << EOF
CLASSPATH=$pkg app_process /system/bin com.koushikdutta.shellproxy.ShellRunner2 [email protected] &
exit
EOF
And this is my output:
Code:
$ adb devices
List of devices attached
9885e6************ device
$ ./run.sh
/data/app/com.koushikdutta.backup-1/base.apk
CLASSPATH=/data/app/com.koushikdutta.backup-1/base.apk app_process /system/bin com.koushikdutta.shellproxy.ShellRunner2 &
exit
pp_process /system/bin com.koushikdutta.shellproxy.ShellRunner2 & <
[1] 31207
[email protected]:/ $ exit
sh: resetreason: can't execute: Permission denied
From the start I didnt understand how the app can access other app data without being rooted and the fact I'm getting permission denied seems to reinforce that. Looks like I'll be contacting the dev instead.
Don't you have a PC? Basically Helium without root simulates a connected PC, allowing app data backup. To activate the app, download the PC program and install, and install the app on the phone. Open app on phone and program on PC, plug the phone in, follow the instructions on the phone, then wait for activation.
Sent from my Galaxy S7 Edge Duos via Tapatalk
My phone is now my PC. I can cast my phone screen to my TV and use a bluetooth mouse n keyboard to do almost anything i can do on a PC
For the few things i cant do, I use a RPi and thats based on Linux. The instructions you gave is exactly what i am doing but using linux instead. The helium desktop 'app' is available on linux according to the support page (its really just a script which runs adb commands).
Since i have adb on Raspbian anyway, i just modified the script to use my built in version of adb as the bundled version is not compiled for ARM. The permission denied message is from the phone itself. So something else is going wrong. When i run the android app though it allows me to make backups but it doesnt look complete to me, much like the Smart Switch backup wasnt complete.
Fyi, i am a web developer by trade but dabble in python and c programming. I am currently writing my own android app to control my custom made home automation system using an API. Thats why i have adb preinstalled. So i am used to dealing with code to work out problems. I will liaise with the dev about the permission denied error as soon as i find the correct repo to report it in!
I've never been able to ge Helium to work reliably on my edge. Most of the time it won't work at all. Crappy unsupported software.
Unfortunately I've not found any solution that backs up everything, or even close to everything. Smart Switch will back up some, RERWARE's MyBackupPro will back up some. And those seem to be the best options out there. It's borderline criminal that Google still hasn't bothered to build a full backup solution into Android.
The Apps themselves should be set to use Google's online backup, but not all of them do. Games mostly follow. On restoring your phone, it will ask you if you want to restore from backups of your apps Google made, but that only works if the app developers were compliant with standards Google presented.
Sent from my Galaxy S7 Edge Duos via Tapatalk
Helium is working even with the permission denied error. The app runs and allows me to make backups but as ever, they dont appear to be complete. For example, as mentioned in original post, the backup only takes the 8MB APK and not the 150MB data. Its the same as Smart Switch.
As to the Google backup, you can now view these backups in the Google Drive app and only half my apps are there and again they dont look complete backups (one backup is apparently 1KB but app manager says it 12MB data).
I noticed that app manager reports data size but even this isnt accurate. If your app stores data in a folder on internal storage or sd card then this isnt counted as data. Only that in the data partition appears to count. My Torque logs are a prime example of this. 56MB of files on internal storage, app manager reporting 292KB data. No backup at all on Google Drive.
Im trying do a nandroid backup using a temporary recovery. Ive tried 'fastboot boot twrp.img' and 'fastboot boot recovery twrp.img' but neither work. Nothing is recognised with 'fastboot devices' which is concerning. I also cant use 'adb reboot bootloader' as the phone just restarts like normal. Samsung and Three have both said they dont lock the bootloader so im at a loss as what to do next :/
That's weird. Helium works for me. I wonder what's the difference.
Sent from my Galaxy S7 Edge Duos via Tapatalk
meyerweb said:
I've never been able to ge Helium to work reliably on my edge. Most of the time it won't work at all. Crappy unsupported software.
Unfortunately I've not found any solution that backs up everything, or even close to everything. Smart Switch will back up some, RERWARE's MyBackupPro will back up some. And those seem to be the best options out there. It's borderline criminal that Google still hasn't bothered to build a full backup solution into Android.
Click to expand...
Click to collapse
THIS ^^ Exactly my thoughts. Without root and TWRP / Titanium you're screwed
Hello!
So I recently rooted my Samsung Galaxy S5 (SM-G900i)
I flashed the kltedd .tar.md5 file through odin (downloaded the .tar.md5 file through Chainfire's CF Auto Root Website)
Everything worked, after going through the whole process my phone rebooted and everything seems normal.
All my data has been preserved and it all works fine.
The only problem is to check that my phone actually has root access I need to download one of those root-checker apps from the play store, but I need to sign into my Gmail account to get to the play store in the first place.
I just wanted to know if it is safe to log into my gmail account on a rooted device - is it possible in any way shape or form that I might have a sneaky keylogger or some spy-ware that could potentially see my Gmail password?
Any help would be appreciated
Sincerely, a noob to XDA Forums.
If you have rooted then there should be a SuperSU app or similar, and when you enter it it should tell you somewhere if root is working fine.
There's an easy way to check for root, which doesn't involve any app, but you need to be able to connect the phone to a PC and you will need USB drivers, and to get your hands on adb.exe (or android-tools-adb package on Linux). Assuming you've done that:
* Enable developer options. (Settings > About Phone, tap Build number 10 times, you will get a popup telling you that Settings > Developer options has appeared.)
* Enable "USB debugging mode".
* Connect via USB to the PC.
* Run `adb devices`.
* You will be asked if you want to accept the debug connection, and possible if you want to enable MTP, say "yes" to both.
* Run `adb shell`.
* Once inside the shell you can type "su[ENTER]". The terminal should freeze and you should get a popup from your SuperSU app asking if you want to grant root access to ADB. If you don't get a popup and "su" fails in the terminal, you don't have root. If you don't get a popup but you get a "#" prompt in the terminal, you have root, but you don't have a root controller app, which is not good (anybody can get root).
Another even simpler method would be to use a terminal app... provided you already have one installed. Most custom ROMs do, stock ROMs don't. Then you just use the same "su[ENTER]" stuff in the terminal.
also, you can bypass the whole thing of logging into your gmail acct and go directly into your phones main screen, go into menu, settings, about phone and tap on the build number until you see the message stating that you are now a developer, back up one step, go into developer options, check the box to allow the installation of third party apps and just download the root checker apk from elsewhere. Sounds compllicated, but its easier than CLI stuff for the uninitiated
---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------
also also, ive never heard of anyone getting a keylogger after merely rooting their phones
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
security should be fine as long as you dont lose your device or download apps from unsafe sites.
as for whether it is rooted or not, already answered above.
Good to see another aussie here.
I'm still a bit of a noob too but happy to help with any endevours regarding phone, especially model specific ones (I have G900I too).
wirespot said:
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
Click to expand...
Click to collapse
really mate!?
i have my rooted S5 with my 3 gmail accounts logged in
and i didnt have any secuirty issue at all in past and now
This is a guide to debloat the KIW-AL10 and make stock Chinese usable.
First download Minimal adb and fastboot from here and install it.
Download HISuite and use that to install huawei drivers
Next Make sure developer options by hitting build number 7 times then open developer options and make sure usb debugging is activated in the developer options.
Plug phone into computer and install drivers, any unknown device will be adb so right click and select choose driver from list then select android devices then adb interface, always choose the older driver version for this phone.
One you have that installed you need to unlock your bootloader a great guide is here
Once you have unlocked the bootloader download install twrp using minimal adb and fastboot
First reboot into fastboot..
First check the device is present. using the command :adb devices
then boot into bootloader using the command : adb reboot-bootloader
if that doesn't work turn off device then switching on quickly hold down the volume down button while inserting the cable into the device
The device should then have a white screen with a robot and say unlocked in green writing
find the recovery image you downloaded and if its a different name rename it twrp.img so you know which one it is, files everywhere can get quite messy !
Now right click on the minimal adb link on the desktop and click open file location..
Now put the twrp.img file into the folder with the minimal adb files and close the window.
now flash the recovery using the command: fastboot flash recovery twrp.img
Voila if everything is sucessful your phone now has twrp recovery !
Next use the following command: adb reboot recovery, if that doesnt work force a shutdown by holding the power button then let the phone boot while holding down the volume up button, it should boot into recovery.
Next MAKE A BACKUP THIS IS VERY IMPORTANT AND WHEN ITS DONE COPY IT TO A SAFE DRIVE DO NOT KEEP IT JUST ON YOU SD CARD IN CASE YOUR CARD DIES ! BECAUSE OF THE NATURE OF THIS PHONE AND THE FACT THAT YOU CANT FLASH NON VOLTE ROMS ON THIS PHONE THIS IS YOUR ONLY WAY OF RESTORING THE PHONE SO GUARD IT LIKE YOUR LIFE DEPENDS ON IT !
Now get a cup of coffee and have a break its not good to rush things
Now to root your phone..
Finish your coffee.
Download supersu from here
Put the zip onto your phones sd card and boot into recovery, select install and select the supersu zip and let it install, once done reboot the phone, it may reboot a few times thats normal dont panic, once the phone has finished booting check you have the su app installed, if so now we can do the rest of the stuff.
Next download google play store from here and install it
After opening the play store and signing in you will probably be told to update google services, let it do it then reboot the phone
Next using the play store download root explorer
Next stage is to make the dialer English. and remove yellow pages.
Using root explorer navigate to /cust/alltelecom/cn/prop
hard press on the file local.prop and select open in text editor using the 3 dots on the top right
Look for the following lines of code ro.product.locale.region=CN or similar
Change this to ro.product.locale.region=GB (or whatever your location is such make sure the country code is in CAPS )
Save the file
Now navigate to /system and open build.prop in text editor and change the following lines of code so they end in County matching code not cn
Example
ro.product.locale.region=GB (or whatever your location is such )
ro.product.locale.language=en (or whatever your location is such )
ro.product.locale.region=GB
Go slow there is lots of lines there but you will see them if you take your time
select save and exit from root explorer then reboot.. viola the chinese and yellow pages is gone !
After reboot you may get a baidu warning about location tracking, dont panic we will kill that bugger next !
Next install system app safe remover from the play store https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB I always use this as its simple and keeps a backup of the removed app (just in case of problems)
Use that to remove all the chinse apps from the system including hivoice or it will interfere with google assistant, they are self explanatory
as they are all in chinese !
Next remove hi app
hi care
huawei id
network location (this is the one causing the nag screen dont worry work it will still work.
then reboot phone, there should be no more warnings about baidu location.
Now to get services google working.
You my have notice that despite installing a google account you contacts havent synced. we will fix that now..
To get google contacts to sync you need to install google contacts sync adaptor 6.0.1 from here
After you have installed it open up system apps and check it permision contacts is allowed, also open the battery setting and check it runs at boot and while screen is off, if there are no options for that ignore that bit and exit.
while you are there check google play services permission are all on especially contacts then reboot
Now install the google app from the app store
next install google assistant from the play store
now install google photos from the play store
Next install google chrome from play store
next install google calendar from the play store
next install google plus from the play store
next install google maps from the play store
next install youtube from the play store
Next install gboard from the play store
Then when all is done reboot the phone
After reboot check all the permissions of the apps and make sure all the google apps run at boot and keep running after screen off or they wont sync etc then reboot again.
Change horrible huawei keyboard to gboard in language settings
Open the google app and setup google and check your contacts have synced. set up the rest of your settings
Get a decent launcher as the huawei one sucks I use nova launcher prime its worth every penny but the free one is still good
Open settings app and click advanced, here you can change default launcher and select default app setting then select assistance and voice input, selectassist app as google select use text from screen and select use screenshot
I think that pretty much it, the rest you should be able to do yourself, have fun and good luck, any questions just ask.
I wrote this guide as there is very little info on the AL10,
Happy modding !
Very useful
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Ed_shred said:
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Click to expand...
Click to collapse
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Ed_shred said:
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Click to expand...
Click to collapse
Repeated the process, ticked a few boxes in SuperSU, seems to be solved for now, thanks...
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
OK, so I have tried quite a few times to install Lineage OS 14.1 and Viper, with both they get stuck in a bootloop. Trying to install Lineage with this guide https://wiki.lineageos.org/devices/kiwi/install, the 'format data' stage is not successful. I get a message saying ' E:Unable to wipe '/data' - unknown file system 'auto Unable to format to remove encryption '.
I'm not totally committed to a custom ROM, but I'd like this phone to work. Any ideas, either how to troubleshoot the ROM flashing issue, or to get the phone stable with the stock de-Chinesed stock ROM? Thanks!