[DEV][N][DP2][CRACKLING]Android N Developer Preview

14th March 2016, 03:48 PM |#11

Member

High Wycombe

Thanks Meter: 6

Quote:

Originally Posted by cleversokol

I've tried this firmware on my phone and I'd like to share both experience and expressions.

Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:

Code:

bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)

Then I tried to unlock the bootloader and flash images:

As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.

I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.

Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one

Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people

: http://forum.cyanogenmod.org/topic/1...ck-cyanogenos/

PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected

Quick Reply Reply

14th March 2016, 05:00 PM |#12

Junior Member

Thanks Meter: 0

Can I use this TWRP? I did not found Wileyfox Swift among supported devices.

Quick Reply Reply

14th March 2016, 05:06 PM |#13

Member

High Wycombe

Thanks Meter: 6

Quote:

Originally Posted by cleversokol

Can I use this TWRP? I did not found Wileyfox Swift among supported devices.

I believe this is the one I've used.

In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.

Quick Reply Reply

14th March 2016, 07:27 PM |#14

Junior Member

Thanks Meter: 0

Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With

Code:

fastboot oem lock-go

it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?

Quick Reply Reply

14th March 2016, 08:24 PM |#15

Member

High Wycombe

Thanks Meter: 6

Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).

If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.

These are your options

Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.

Quick Reply Reply

15th March 2016, 06:13 AM |#16

Senior Member

Johannesburg

Thanks Meter: 31

I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?

Quick Reply Reply

15th March 2016, 09:39 AM |#17

Senior Member

Thanks Meter: 321

Quote:

Originally Posted by yasteellutch

System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/show....php?t=2588979

Quick Reply Reply

15th March 2016, 02:26 PM |#18

Senior Member

Johannesburg

Thanks Meter: 31

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

Quote:

Originally Posted by yasteellutch

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio

It keeps on saying sending sparse system img(0kb)

Quick Reply Reply

15th March 2016, 02:37 PM |#19

Senior Member

Thanks Meter: 321

Quote:

Originally Posted by yasteellutch

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

It keeps on saying sending sparse system img(0kb)

Just try this
http://androidhost.org/P2XKs

unzip to your root directory - copy Android N images to this directory and give it a try.

Quick Reply Reply

15th March 2016, 03:43 PM |#20

Senior Member

Johannesburg

Thanks Meter: 31

Quote:

Originally Posted by mermigas

Just try this
http://androidhost.org/P2XKs

unzip to your root directory - copy Android N images to this directory and give it a try.

This is what I get

Attached Thumbnails

Click image for larger version

Name: Untitled.jpg
Views: 144
Size: 140.0 KB
ID: 3683871

Quick Reply Reply

15th March 2016, 05:57 PM |#21

Senior Member

Johannesburg

Thanks Meter: 31

Quote:

Originally Posted by mermigas

Just try this
http://androidhost.org/P2XKs

unzip to your root directory - copy Android N images to this directory and give it a try.

Funny. When I get the OEM variable it says Device tampered : False but Device Unlocked : True. Could this be the issue?

---------- Post added at 03:57 PM ---------- Previous post was at 03:41 PM ----------

Quote:

Originally Posted by yasteellutch

Funny. When I get the OEM variable it says Device tampered : False but Device Unlocked : True. Could this be the issue?

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.013s]
finished. total time: 0.014s

Quick Reply Reply

Guest Quick Reply (no urls or BBcode)
The following errors occurred with your submission

Okay
Message: Posting Quick Reply - Please Wait

Most Thanked

Thread Search

Analysis & Opinion

XDA-Developers Wishes You a Happy New Year!

2016 in Review: What was the Biggest Disappointment this year?

Editorial: Bezels in 2016, and the Trends that Will Shape Smartphone Designs in 2017

Galaxy S7 Versus Galaxy S7 Fake

Stable Nougat for OnePlus 3 and Nougat Open Beta 1 for OnePlus 3T Are Here

Top Forum Discussions

Android 7.0/EMUI 5 is Available For The Huawei Nova Without Unlocking the Bootloader

An Unofficial Build of TWRP is Available for the ZenWatch 3

XDA Subforums Now Live for Honor 6X!

Full ADB Root, System Read/Write, and dm-verity Off Achieved for All LG G5 Variants

Snapprefs Gets Updated to 2.1.0, Adds Support for 9.39.5.0

Guide for Full ADB Root, System RW, and DM-Verity Off on the Sprint LG G5

Unofficial AOSP 7.1.1 Nougat Lands on the MT6753-based Ulefone Metal

[DEV][N][DP2][CRACKLING]Android N Developer Preview

Top Threads in Swift General by ThreadRank

vBulletin Message