Related
i have these specs:
model number: HTC Desire Z A7272
IMEI SV: 01
Android Version: 2.2.1
kernesystem: 2.6.32.21-g6e170e7
[email protected] #1
softwarenumber: 1.82.405.1
i am guessing that i need to follow the downgrade guide, and the root guide next.
or has the circumstances changed since the guides was written ?
This is the best guide and is regularly updated http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my HTC Desire S using XDA Premium App
Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App
..
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started
krankdroid said:
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started
Click to expand...
Click to collapse
You need to change to the directory where adb is. It will be something like c:\>Android-sdk\platform tools
Sent from my HTC Desire S using XDA Premium App
krankdroid said:
DroidExplorer instead of ADB ?
Click to expand...
Click to collapse
Yeah it's so much easier to manage then ADB. It's basically like using Windows Explorer but for your phone, so it's really easy to add apps and files or whatever to your phone without having to remember to use ADB codes (especially if your a beginner like me).
It comes with the Android SDK everything setup so you don't need to deal with the setup of the ADB which saves the hassle and time. All you would need to do is just point CMD in the path of the ADB inside Droid Explorer and you're good to go! I would post a link for you but I cant obviously, so just give it a Google and you'll find it.
Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.
redpoint73 said:
Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.
Click to expand...
Click to collapse
I agree to delete imei number
Sent from my HTC Desire Z using XDA App
ok..
so now ADB is working with my phone..
the next step is downgrading. that will wipe my device. so how on earth do i take a backup, if i need to wipe my device, before i can root, so that i can take a titanium backup?
is it just tuff luck for me?.. goodbye apps and widgets? or can i backup before i root ?
You can use any backup/restore app to do the job.
The guide someone posted earlier in the thread works flawlessly there're only a few things to remember:
When using ADB when pushing files make sure you're in the same folder as the file itself otherwise it'll return the error "No such file or directory".
If you followed the guide to setting up ADB then you will have changed "Path" under "System Variables" in "Environmental Variables" (Right-click My Computer > Advanced tab > Environmental Variables) to include the following:
";C:\Android\android-sdk\platform-tools;C:\Android\android-sdk\tools"
(No quotes and leave out the semicolon at the beginning if there already is one.)
Change C:\Android\android-sdk\ to wherever ADB is on your comp and you can issue ADB commands from any from almost anywhere on the comp rather than having to be in the same folder as it.
Other than that I can't think of much else other than to follow the instructions and ask for help if you get stuck.
I got ADB working..
I will stick to posting if i run into any problems.
But before i can root i need to downgrade my device first. And this procedure will wipe my phone..
I also need to root before i can do a titanium backup.
I have taken a mybackup pro backup. But that is only apps, media and data. And not a complete backup. As i understand it i cannot create a real backup unless i root right?
And to root i need to perform a downgrade that will wipe my device..
So no matter what i will loose all my stuff if i want to root..
Via HTC Desire Z
Your Gmail and Contacts are synched to Google, so no need to back those up. If you want to backup your SMS and MMS, I have been using SMS Backup+, and it works well. It backs up SMS/MMS to Gmail, and restores SMS to the phone (unfortunately does not restore MMS pics to the phone, but those will be saved on Gmail). It also supposed to backup the call log, but it doesn't restore properly for me after switching ROMs.
If you want to backup things like games saves, root is usually need to access those files. Although, there are apps on the Market to backup your Angry Birds progress, if you want that!
Any other things you want backed up before you downgrade?
If you follow the guide to root your Desire Z you shouldn't run into much problems.
There's a few recent post on the forum with similar questions and will be more then happy to help you get rooted. Like I mentioned to someone earlier, I rooted by DZ just now for about 2weeks. Yeah I did brick my phone twice but I did manage to get everything back to working and rooted. My only mistake was that I hadn't created and fallowed the goldcard process but once that was done anything to do with ADB worked like a charm.
i am now trying to learn the INFOCID of my device..
but something is up.
Code:
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
the info i obtained from the first command was:
Code:
vision PVT Ship S-on
Hboot-0.85.0010
microp-0425
radio-26.04.02.17_M2
eMMC-boot
no INFOCID there as far as i can see
could someone help a newbie out ?
I need to know my infocid before i can downgrade
KalC87 said:
Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi hoe did you do with droid explorer i can't there is a tutorial or something??
krankdroid said:
....
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
....
Click to expand...
Click to collapse
I got fastboot from the HTC Dev Center.
Hi this is my first thread and i really dont know how this works but heres the problem
i bought a nexus 4 16gb from a guy on craigslist and it has a wierd rom in it, it is still 4.2 and i am unable to get updates on it. i browsed around and landed on a forum that said about it being some kind of debugger/developers rom that google uses. i dont have a lot of feature i can't connect it to computer to root it and neither can i transfer file from computer for exaple music or pictures.
The build number is:
full_mako-userdebug 4.2 lgep19
eng.seungju24.choi.20121114.105751 test-keys
If you want your phone back to stock and unroot you'll need to access a PC and follow this guide.
http://forum.xda-developers.com/showthread.php?t=2010312
This will put the phone how it comes out of the box. Otherwise if rooted and has custom recovery why not stay rooted and flash different 4.2.1 roms?
Sent from my Nexus 4 using xda premium
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
Also this video will help too. He has a folder for download with everything you need.
All you need is to type in commands.
https://www.youtube.com/watch?v=2Se0N86qsJE&feature=youtube_gdata_player
Sent from my Nexus 4 using xda premium
What os do you have on your computer?
Sent from my Nexus 4 using xda app-developers app
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Not working
rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this:
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.
irfan9490 said:
It is giving me a error message
" fastboot" is not recongnized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this: http://dl.google.com/android/installer_r21.0.1-windows.exe
It still isn't working
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse
irfan9490 said:
rr5678 said:
Oh yeah, you don't have the Android SDK installed, do you? Well download and install this:
Click to expand...
Click to collapse
hey thanks for your reply i have tried it with the android SDK but it still isn't working. i would really appreciate if you could help me thanks you.
Click to expand...
Click to collapse
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat
ANother Error
rr5678 said:
Are the drivers installed or does it say unknown device?
If the drivers are installed, copy fastboot.exe from the attachment and put it in the same folder as flash-all.bat
Click to expand...
Click to collapse
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money
irfan9490 said:
Now there is another error that says the AdbWin.Api.dll is missing. Really sorry for bothering you again and again but the phone really lags and i paid almost 500 for it like 2 weeks ago and now they have it in stock. if i could fix it i would feel better about spending my hard earned money
Click to expand...
Click to collapse
Okay, try adding these to the same directory.
Still not working.
rr5678 said:
Okay, try adding these to the same directory.
Click to expand...
Click to collapse
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.
irfan9490 said:
Thanks for the help it cleared the .dll error but i have attached the screenshots of what i got as it did not change the rom.
Click to expand...
Click to collapse
open a command prompt in that directory and type fastboot oem unlock. then try again
Thanks you very much it works a lot better
now.
Sent from my Nexus 4 using xda app-developers app
rr5678 said:
1) That's a Debug ROM
2) It shouldn't be used as an actual ROM. Download this: https://docs.google.com/uc?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU&export=download
3) Extract it.
4) Turn off your phone, then hold Power and Volume Down. When you see the Android on it's back, connect the phone to the computer and run the flash-all.bat in the folder.
5) Wait and then you're done.
Click to expand...
Click to collapse
I am VERY thankful for this thread. It helped me rid a company phone of that garbage Debug ROM. Thank you very much!
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.
The WileyFox Swift 2 Plus is not a bad looking phone, the case feels good in my hand. It is almost small and light enough to fit into my shirt pocket should I need to.
It runs CyanogenOS which is an improvement on the standard bloated Google Android and is to be applauded.
3Gb for the System and 32Gb Storage, 2.4GHz WiFi, Dual Sim, External SDCard, NFC, Android Pay, Android Beam , FingerPrint recognition, 4G, 16Mp/8Mp cameras, 5" screen - great stuff especially for the price. It is however, designed as a city phone not an everywhere phone that much is apparent.
There are a number of downsides :crying:
The second SIM slot doubles up as the Ext SDRam slot - one or the other not both - what an epic fail !!!
Can't actually use the SDcard for backups or data or media - bit of a waste of space really. You need to root the phone and install SD Fix or similar.
It only works with 2.4GHz WiFi which is a disgrace given my ancient Xperia T covers 5GHz as well.
There is no real GPS only A-GPS which needs an internet connection to work - no good if you have a poor or zero mobile signal. This is really such a waste of time even implementing this instead of the real thing.
Only the Google versions of photo album and media player (which don't find local files), mail(gmail) , calendar, calculator etc are installed. If you like having to use a data connection and Google knowing everything you do then fine. I don't which means I have to install apps covering those functions. Shame I can't just install those I used on my Sony Xperia. If you already have favourites its not a big deal. If you don't then you have to start loading and trying out Apps to find the one you like.
Having set up the phone to your liking it would be nice to be able to save it that way. Which you can't without Rooting the phone.
To make the best of it you need to Root the phone - this is to be able to install effective anti-virus, firewall and anti-theft software. To be able to install Titanium Backup in order to actually backup the current state of the phone including apps and data to the SDcard as well as the cloud.
And remove the Apps that you don't use or don't care to have installed.
Would you use a PC without that type of software ? I suspect not - So why make a phone that you can't install the protective software on to ?
It is very simple to unlock the Bootloader and then Root the phone using SuperSU just using the phones developer options. No need to install ADB on the PC or install TWRP on the phone if you don't want to use a custom ROM. Unfortunately it invalidates the manufacturers warranties. :crying::crying::crying:
This could have so easily been a perfect phone, unfortunately a couple of poor cost cutting decisions have more or less ruined it.
Me ? I have already given away this phone after just 3 days, much to my disappointment.
Isn't A-GPS built on top of GPS and purely there for lock startup speed?
You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...
Even better
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:
Just managed to pick up one of these practically brand new for only £100 for a friend.
Really nice build quality and look of the phone and packaging. CM13.1 looks nice and any bloat can be quickly disabled or even uninstalled. 3GB Ram is great as sitting here now, this phone has 2GB just sat there free. (Unlike the Nexus 9 for example!) If I was nit picking, the screen could be better and the fingerprint reader isn't as fast as my One Plus 3, (Not to be expected given the price.)
If I had this in front of me, a P9 Lite, and the standard Moto G4 for the same cash, I'd pick the P9 Lite due to its better screen. I'd pick this second due to the extra RAM and fingerprint reader, and the Moto last. If I had to pick a phone to last 2 years, I'd pick this over the P9 as CM13 is better than the strange Huawei stuff.
If Wileyfox could drop the price to £160, I think they'd be onto a real winner.
bahjesaispas said:
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:
Click to expand...
Click to collapse
Just bought today can you give run down how to unlock bootloader:good:
stevegtrlmk said:
Just bought today can you give run down how to unlock bootloader:good:
Click to expand...
Click to collapse
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)
Demostrike said:
Isn't A-GPS built on top of GPS and purely there for lock startup speed?
Click to expand...
Click to collapse
Nope A-GPS is a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
If you are running a WileyFox Swift with Cyanogen you will find that any of the GPS test apps will say there is no GPS.
A-GPS does NOT work without an internet connection.
Some phone use A-GPS to speed up their lock within built up areas.
Having said that the Swift running the Android v7.1.1 Nougat package the GPS has been enabled and the GPS Test tools now work.
Go figure why it wasn't enabled in the first place.
rivierakid said:
You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
Depends what you want to use the SD card for, maybe something like saving your Titatium backups which can be removed from the phone if it is dead. And if you want dual SIM you can't use the SD card. And you need to root the phone to use the Marchmallow SD card unlock.
If you let the phone use the SD card as extended memory it is encrypted and you can't read it without that phone - thanks Google.
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
Nope SOME phones use A-GPS to speed up lock within built up areas but it is really a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
check your facts.
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
And if you don't like the pre-installed versions you need something like Titanium to remove them.
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
And the UPDATES stop the moment you unlock the BootLoader let alone Root the phone.
Anti-Theft, Anti-Virus, Anti-Malware, Titanium Backup, Nandroid Backup all need ROOT.
The Cyanogen Anti-Theft stopped working when the website closed.
The point I was making is why should you have to 'break' your phone to protect your investment?"
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
LOL - no Cyanogen is no more , although there is a movement to Lineage which may grow into a Cyanogen replacement
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...
Click to expand...
Click to collapse
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.
SMessy said:
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.
Click to expand...
Click to collapse
Get your facts right, just about all phones use aGPS. And all phones lose updates when rooted. You make generic points and a tribute them to a particular device. Sad.
Sent from my Lenovo P2a42 using Tapatalk
MoHaG said:
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)
Click to expand...
Click to collapse
Reboot into fast boot is that within the phone or when your connected to computer :good:
stevegtrlmk said:
Reboot into fast boot is that within the phone or when your connected to computer :good:
Click to expand...
Click to collapse
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)
MoHaG said:
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)
Click to expand...
Click to collapse
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing
stevegtrlmk said:
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing
Click to expand...
Click to collapse
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Thanks for that I have not tried yet but will do soon much appreciated:good:
image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp
stevegtrlmk said:
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp
Click to expand...
Click to collapse
Minimal ADB and Fastboot is a PC based program. I have provided link below for you.
https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
Once installed you place the file to be flashed in the program folder with the other installed core program files in directory.
If you run the program you get the command prompt window as displayed in post. This is where you run the Fastboot common I advised you about in earlier post.
So in the command window type and execute:
fastboot flash recovery twrp-3.1.1-0-marmite.img
You might wish to read this thread too on XDA
https://forum.xda-developers.com/showthread.php?t=2317790
Hope this helps Robert.