Database Users

[Q] update gone wrong -help - friends phone!!

Hi All, I have searched but not found an explaination thats clear to me.... here goes.
Ideos X5, mine, updated with GB from Huewai site - beta version, works great!!! beter battery, faster wireless etc... update when flawlessly using instructions included in the update file.
Tried to update my friends ideos x5 exactly the same but a white one, and first stage loading the update went fine but then when it restarted it to load 2nd update file, - the 1k one, it just goes to pink screen. Obviously not seeing the sdcard...
Its not bricked because it seems to work fine... just appears to be missing some apps like the wireless/bluettoth/gps switcher that appears on mine when i pul down the notification screen, also maps says it has an error , and he does not have the 'beyond the sky' theme.... and only default keyboard laylout that pretty much sucks.
Now - the question is - can i remove the sd card from my phone, put it in pink screen mode and copy the image folder to my pc then copy it out to his phone? will that work?
I can't seem to flash it agian as it appears to not see the sdcard in flash mode hence why it goes to pink screen mode.

What phone model do you have? Which version of rom (from which thread) did you download?
Probably you need to do a downgrade. You have a thread for that.

It was the update from the manufacturers web site as I stated above - the beta vresion of gingerbread, Ideos X5 U8800 is the model of phone, not the pro version.
As I sid it appears to be running GB and the 'about phone' screen confirms this, just the apps are not all there and the boot up is different, looks like its loading frodo intially with the IDEOS logo then an android title appears, then it loads up to the gb lock screen.

Use the update from this thread (B518): http://forum.xda-developers.com/showthread.php?t=1369296
It has only one step (2 steps are joined into one) and work fine
Edit: You can try using internal SD if it doesnt detect external... btw: Do you have fast bot turned off?

thanks fo ryur reply, but it did not help, this is the same version we used to get where we are at now.... it is two step upgrade, the last update file is 1k and has all the settings and apps config... or so it seems.
We have managed to get the update to complete, but there is one strange side effect, the internal sd only has 6 or 7 folders whereas my phone I upgraded 2 weeks ago has lots... I wonder if its write protected it or something.
to get round the "unable to see external sd" after running first update file - hence unable to load second file - by connecting to computer and replacing the imgage folder on the internal sd card with the ones from my phone. On restarting it imediately found external sd and the dload folder and completed its update.
Can some one explain why this worked? I don't understand why it did, but would like to.

[Q] Intentionally deleted android system

Hello,
I'm new to the forums and I'd like to introduce myself. I am a Web Developer, 19 years old and I'm from Greece. Right now I own a Sony Ericsson Xperia x10 mini and I rooted it. I had this program installed from Android Marketplace that allows you to delete applications.
So guess what... I deleted several applications for testing purposes and I knew that if I uninstall Android System it would break everything.
I did that epic "mistake" for testing purposes (don't try this).
The thing is how do I fix this? I have spent some time reading through the forums here and installed Flashtool and downloaded the ftf file (X10a_v2.1.update-1_2.1.A.0.435_Generic.ftf) in C:\Flashtool\firmwares directory.
What I have to deal with right now:
- My mobile phone switched off when deleted Android System so I decided to boot it to see if any error messages comes up.
- Now my phone won't power off due to the lack of Android System. So I have to use a torx screwdriver to remove the screws and take off the battery (because Flashtool requires the phone to be switched off) but unfortunately the torx I have is one size bigger than the required one for xperia's screws.
- I guess I have to wait until the battery is dead or I should just get a proper torx screwdriver.
The thing is that I have another Xperia x10 mini as well (works for now - didn't try any uninstall) and connected it to FlashTool and followed the instructions to flash it but I keep getting this error message:
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
I tried to figure out what's causing this and I end up with the "locked bootloader solution". I tried the instructions read here: unlockbootloader.sonymobile.com/instructions but when I typed *#*#7378423#*#* no service menu was available...
That happened to the working xperia phone. How would I possible do that on a broken xperia?
Any suggestions would be highly appreciated!
We're all learning through our mistakes after all.
Warmest Regards,
George Girtsou

Tutorial for getting Nokia Here/Drive maps onto the external SD card on a Lumia 532

Hi guys,
I bought a Lumia 532 for navigation purposes for my parents,
as they have absolutely no clue about smartphones and this
should be the easiest handset to work with. Also, I am totally
new to this operating system, because I am using Android and
iOS.
Now I am searching for a complete tutorial on how to get
the Nokia Here maps saved on the external SD card. It seems,
the old method with Lumia Storage Check Beta is not working
or existing anymore.
I found bits of information here and some there, but there is
just no single complete tutorial going from step 1 to x. :\
Thanks a lot in advance.

Interopunlock phone, install wptweaker...push some buttons...

Yeah, I was searching for a complete tutorial, but someone
just helped me in another thread.
Thanks, anyway.

Lumia 532 too

[DANGEROUS TOOL][DO NOT USE!][READ FIRST!!!] Trim Area Tool

Trim Area Tool​
Hello! First of all sorry for my bad english words I will try to explain what this tool mean. I am working on trim area dump .ta to .img converter. Whole idea is to dump drm key which is stored in ta unit 1046b and dump the rest of units and further convert (reconstruct) that .ta dump to fully functional .img dump. Whole idea is based on thing which I found in my trim area dump unit 1046b which is somehow doubled on my unmodified locked TA and by the way not deleted after unlocking. I thinked to root phone by unlocking device, get backup unit 1046b, reconstruct trim area, flash reconstructed trim area to make phone locked as before unlocking. Inded it can be done (unconfirmed curently) but... Later things is confirmed on other phones that not all phones have that doubled unit so that mean not all phones have the same trim area. In general my idea was to decode that mistic trim area. I have done things, its decoded partialy but not all since some devices don't have the same headers of the units, for example some device headers starts with C1E9F83Bffffffff but some with C1E9F83Bffffff32 and some with C1E9F83B32323234... I have done some tests to an device (z3) which have broken screen. That phone had that diferent unit headers which is not like on my phone c1e9f83bffffffff, I have reconstructed trim area, flashed back, and this is a report -> http://forum.xda-developers.com/showpost.php?p=69926765&postcount=117 and this one -> http://forum.xda-developers.com/showpost.php?p=69928391&postcount=119 and this one -> http://forum.xda-developers.com/showpost.php?p=70003707&postcount=153
Whole story starts at page http://forum.xda-developers.com/xperia-x-performance/how-to/dirtycow-temp-root-t3503918/page5 please read all posts if you are interesting for trim area things and things which I thinked to do! By that way you will understand better about our tool and idea about a tool!
Trim area format is explained in this post -> http://forum.xda-developers.com/showpost.php?p=69865938&postcount=64 . Problem by now is we don't know how safe is reconstructing some trim area, for example that mistic diferencies in bytes (ffffffff) on some phones and (32323234) on some phones and also some diferent on some phones is a problem by now. What that bytes mean and or why it differs on some devices, I don't know. My tool reconstruct that and makes all ffffffff. The same things can be seen in unused blocks, for example on some devices its filled with 0xff and on some devices with 0x10 and on some devices with 0x32. Why I don't know. My tool makes it all 0xff.
I can reconstruct all units from .ta and can produce .img, but I can not confirm if it will work since testers for that thing is need! Tool is in early stage and not all features is implemented with reason: need to be confirmed one by one. Curently I have done only basic reconstruction which didn't change units data.
Only change headers and unused blocks and make them all with 0xff. At the end tool regenerates hashes of the partitions, thats all by now. I don't know how safe it is at all!
I have done trimarea_tool (command line tool), and that tool nothing change in trim area dump other than unit headers (I have not implemented the rest of my tools since undocumented trim area is still undocumented and very risky is touching trim area, so I not included the rest, it will be public somedays when things gone fully tested), partition hashes and unused blocks, it cleans that 32323234 bytes and writes ffffffff instead and regenerates hashes, thats all by now. Unit data is the same. I have included ton of checks, for example if you try to modify your original ta dump, tool will not generate reconstructed trim area, if size is different, if trim area is not 0x200000 bytes long... and many more. Since we are at initial stage about trim area in general we can't know how safe is playing with trim area, @itsux is only one who flashed reconstructed trim area and reported no hard brick. I must notify you now with red words DO NOT FLASH IF YOU NO WANT TO RISK!!! THIS IS VERY DANGEROUS AND MAY HARD BRICK YOUR PHONE - MEANS KILL FOREVER!!! DO NOT USE ON A WORKING PHONE, THAT IS A RISK!!! Use only if you have broken phone for example working phone with not working or broken screen and you no need that phone, don't flash on daily phone! Itsux is only one who tested on his Z3 phone which is with broken screen, I have modified his trim area the same way, he flashed back that trim area and reported here that his phone is not hard bricked. Again I don't know how safe things is so I am not responsible if tool kills your phone, use at your own risk!! But if you realy want to risk and probably kill your own phone please report what happened at least, it would help further development on this tool!
How to run tool:
First of all this tool is not a standard application so you can't open it like a regular application by double click! Tool is a command line tool so it must be run trught your windows command prompt or trought an batch file! Tool reguires only one parameter, parameter is you TA.img file, e.g:
Code:
trimarea_tool TA.img

Great progress.
I'll think about letting you mess with my Z5s TA [emoji14] Also I'll PM you the Z3 and Z3C TA images as promised in the PM later.
Sent from my D6603 using Tapatalk

Sorry, I don't really understand the purpose of this project, since TA backup is already achieved on new series?

Yes thats a true, dump is achieved, but somedays for example when new xperia lines comes out and there was no root possible (android is more and more secure) we can use further tool to convert unlocked trim area to locked one for example. What we can do with unlocked bootloader that is a very clean I'm in hope

p0kemon said:
Yes thats a true, dump is achieved, but somedays for example when new xperia lines comes out and there was no root possible (android is more and more secure) we can use further tool to convert unlocked trim area to locked one for example. What we can do with unlocked bootloader that is a very clean I'm in hope
Click to expand...
Click to collapse
So u are trying to fix already UB phone with no ta backup to return to completely fixed drm key? wow now i understand XDD Appreciate your work

KWOKSFUNG said:
So u are trying to fix already UB phone with no ta backup to return to completely fixed drm key? wow now i understand XDD Appreciate your work
Click to expand...
Click to collapse
No...the purpose of this tool would be to reconstruct the trim area from a locked bootloader phone so you don't have to wait for an exploit to be found to root (temp root) on future firmwares to backup your TA when all known exploits are patched..
If you already unlocked there nothing that can be done

-DM- said:
No...the purpose of this tool would be to reconstruct the trim area from a locked bootloader phone so you don't have to wait for an exploit to be found to root (temp root) on future firmwares to backup your TA when all known exploits are patched..
If you already unlocked there nothing that can be done
Click to expand...
Click to collapse
Thats right! By the way we still need system user at least in order to dump unit 1046b trought libta.so Hope we get better way when it need.
One more thing, we don't know for sure if drm key is maybe just an generic key for example one which we can enter for example, right? It must be tested first before things gets comfirmed.

p0kemon said:
Thats right! By the way we still need system user at least in order to dump unit 1046b trought libta.so Hope we get better way when it need.
One more thing, we don't know for sure if drm key is maybe just an generic key for example one which we can enter for example, right? It must be tested first before things gets comfirmed.
Click to expand...
Click to collapse
Even better
By the way I got a Z3 with a detached front panel, which is just collecting dust right now as I bought a Z5p after the Z3 broke...
The Z3 is fully functional (the screen colors are just washed out), it is rooted with a locked bootloader (never was unlocked)...I can totally test things on it for you, no problem if it bricks

-DM- said:
Even better
By the way I got a Z3 with a detached front panel, which is just collecting dust right now as I bought a Z5p after the Z3 broke...
The Z3 is fully functional (the screen colors are just washed out), it is rooted with a locked bootloader (never was unlocked)...I can totally test things on it for you, no problem if it bricks
Click to expand...
Click to collapse
That would be great realy! I have done some updates to tool right now, forgot to disable "supported device" check, by now all 2mb trim areas is supported. If you going to try please report what happened!

Some updates... now tool generates two reconstructed formats .img and .ta
.img format is the same like your ta.img dump, just reconstructed
.ta format is just an text file which contains the same data like one from your dump from flashtool, one to four .ta files is created and every one contain its data coresponded to trim area partition number, just reconstructed

Today I have received xperia z1 compact with broken screen, on my supprise I started momentaly working on tests to ta, first thing which I done was reconstruction. What I have done? Since unit 8b2 is unit which is created after unlocking, unit with the same size, unit in the same partition 2 like unit 1046b which get deleted after unlocking... what I tested? Partition 020002 (mean partition 2, part 0), unit 1046b was in partition 020002, now it is in partition 020202 (which is seccond part of the partition 2, in most case), unit 1046b is now in partition 020202 as a replacement to unit 0b2, comfirmed sucess! Just replaced unit 8b2 with one 1046b, reconstructed hashes and I can finally say its success, first device successfuly relocked! Device is locked again the same like before unlocking, all drm keys is with status OK! So guys project is sucesfull! Next thing which I going to test right now is that 32323234 bytes and things...

One more thing! Next test was now:
unit headers which was on xperia z1 compact as C1 E9 F8 3B FF FF FF FF is changed to C1 E9 F8 3B 32 32 32 34, which is totaly the same like z3, and unused blocks which was filled with FF now is changed to 10, reconstructed trim area, updated hashes, flashed, what happened??
Whola!! Done.
Drm keys and thing is with status OK which mean success on z1c, comfirmed successfull reconstruct on z1 compact. I am still afraid to other device models, how safe is on other devices or newer devices I don't know! Probably these bytes which differs on other models (32 32 32 34 on some and on some diferent...), I think can be changed to whatever we want. Maybe these bytes is just an idication for unit changes. On other device I think changing these bytes to FFFFFFFF probably must work the same, I don't know realy how safe is. Be warned again, TOOL IS STILL NOT A SAFE UNTILL SOMEBODY CONFIRM SAFE, HARD BRICK CAN HAPPEN, DO IN MIND THAT! I'm still need somebody confirm before I finalize tool.

p0kemon said:
Today I have received xperia z1 compact with broken screen, on my supprise I started momentaly working on tests to ta, first thing which I done was reconstruction. What I have done? Since unit 8b2 is unit which is created after unlocking, unit with the same size, unit in the same partition 2 like unit 1046b which get deleted after unlocking... what I tested? Partition 020002 (mean partition 2, part 0), unit 1046b was in partition 020002, now it is in partition 020202 (which is seccond part of the partition 2, in most case), unit 1046b is now in partition 020202 as a replacement to unit 0b2, comfirmed sucess! Just replaced unit 8b2 with one 1046b, reconstructed hashes and I can finally say its success, first device successfuly relocked! Device is locked again the same like before unlocking, all drm keys is with status OK! So guys project is sucesfull! Next thing which I going to test right now is that 32323234 bytes and things...
Click to expand...
Click to collapse
You meant that you repair TA area of unlocked device without original TA backup?

Desperanto86 said:
You meant that you repair TA area of unlocked device without original TA backup?
Click to expand...
Click to collapse
Yes!

p0kemon said:
Yes!
Click to expand...
Click to collapse
Dude, its the epic win! In future all sony users can forget about TA backup! You should do DONATE button in your profile!

Desperanto86 said:
Dude, its the epic win! In future all sony users can forget about TA backup! You should do DONATE button in your profile!
Click to expand...
Click to collapse
There is only one problem though, reconstruction need drm key which we need to dump first

I'm analysing now cryptography and can not understand some thing. For example..
1. Unit 8b2 is unit created after unlocking.
2. Unit 1046b is unit which is deleted, it had drm key.
Unit 8b2 is just a key which hash is in unit 7DA (RCK_H= sha256 hash), if we convert 8b2 unit data which is in hex to binary and use it to get sha256 hash we get the same sha256 hash as one in unit 7DA. Unit 8b2 have size the same like unit 1046b, only main diferencie is 8b2 is hex string but 1046b is binary, booth have same size. Unit 1046b after unlocking is replaced with unit 8b2. I am pretty sure there is something tricky between unit 1046b and unit 8b2 since one is hex string and seccond is bin, booth units have the same size! What you think? Do we can reconstruct drm key somehow?

http://newandroidbook.com/Articles/aboot.html Ok. Found some articles how to disasemble aboot, tommorow I will see what aboot says about 1046b

Soo complicated for my head, can't get . Anybody look in .c what is a usage of the ta unit 1046b?? @the_laser , @Androxyde ..anybody?

p0kemon said:
There is only one problem though, reconstruction need drm key which we need to dump first
Click to expand...
Click to collapse
but to dump a BL-locked TA partition we still need a temporary root exploit right?
I can't get it, sorry XD
EDIT: reading better in the original thread, i understand that you can dump the interesting units (NOT the whole TA) using flashtool even on locked devices.
so even without a root exploit, the DRM key could be dumped using Flashtool, TA reconstructed and flashed back after unlocking the bootloader.
And, if i understand well, the TA reconstruction would not include the unit that relocks the bootloader (like it happens when you simply restore the TA backup).
Is it right?

WileyFox Swift 2 Plus observations

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.