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

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

15th March 2016, 06:06 PM |#22

Member

High Wycombe

Thanks Meter: 6

This won't be the issue.

Device tempered goes for a flag indicating modifications have been made.

Device unlocked is a flag designating that the bootloader can be flashed with custom unsigned images (as in TWRP/CM Recovery/ the "seed" boot image/ CM13) and so on.

As you are using Windows, I would recommend you to try with Ubuntu or any other live usb thumb drive with Linux to try the fastboot terminal method.
You can google how to make one (personal recommendation- Win32 Disk Imager to create the bootable thumb drive).

Quick Reply Reply

15th March 2016, 07:47 PM |#23

Senior Member

Johannesburg

Thanks Meter: 31

Tried it with Mint. Same result

---------- Post added at 05:40 PM ---------- Previous post was at 05:36 PM ----------

I think its my USB cable. I got a crappy cable. My original Wiley cable broke .

---------- Post added at 05:47 PM ---------- Previous post was at 05:40 PM ----------

Nope not USB cable.

Quick Reply Reply

15th March 2016, 11:57 PM |#24

Member

High Wycombe

Thanks Meter: 6

Quote:

Originally Posted by yasteellutch

Mmmm, that looks bad. Try to restore it with QFIL before going to custom ROM.
Hopefully the partitions won't be corrupted.

Quick Reply Reply

16th March 2016, 06:59 AM |#25

Senior Member

Johannesburg

Thanks Meter: 31

Quote:

Originally Posted by Pak0St

Mmmm, that looks bad. Try to restore it with QFIL before going to custom ROM.
Hopefully the partitions won't be corrupted.

I did that . I used QFil and tried flashing N

Quick Reply Reply

17th March 2016, 06:33 PM |#26

Senior Member

Johannesburg

Thanks Meter: 31

Worked

Quote:

Originally Posted by yasteellutch

I did that . I used QFil and tried flashing N

Problem solved. TWRP method worked. Only confusion was it said No OS but the DP1 replaced recovery then booted

Quick Reply Reply

The Following User Says Thank You to yasteellutch For This Useful Post: [ View ] Gift yasteellutch Ad-Free

18th March 2016, 07:33 AM |#27

Senior Member

Thanks Meter: 64

Quote:

Originally Posted by yasteellutch

Problem solved. TWRP method worked. Only confusion was it said No OS but the DP1 replaced recovery then booted

Hi bro,
Does flashing these erase SDcard (pictures, movies, etc.)?
I wanna give this a try today.
Thanks

Quick Reply Reply

18th March 2016, 12:48 PM |#28

Member

Thanks Meter: 17

Quote:

Originally Posted by halifage

Hi bro,
Does flashing these erase SDcard (pictures, movies, etc.)?
I wanna give this a try today.
Thanks

external sd card no! so make sure you've got all you want on there. always best to always make a full backup IMHO

Quick Reply Reply

The Following User Says Thank You to ReneX10 For This Useful Post: [ View ] Gift ReneX10 Ad-Free

18th March 2016, 01:05 PM |#29

Member

High Wycombe

Thanks Meter: 6

Quote:

Originally Posted by yasteellutch

Problem solved. TWRP method worked. Only confusion was it said No OS but the DP1 replaced recovery then booted

Great! I'm happy that your device is up and running

Hopefully with less emergencies from now on

Quick Reply Reply

18th March 2016, 02:12 PM |#30

Senior Member

Thanks Meter: 64

Failed tomount '/system' (Invalid argument)

I flashed the Zip in TWRP and that's the message i get at the end of the installation process even though TWRP says installation was successful.
When i reboot, the phone gets stuck at Wileyfox logo then reboots again to get stuck there.
Any solutions please?

Quick Reply Reply

18th March 2016, 03:02 PM |#31

Member

Thanks Meter: 17

Quote:

Originally Posted by halifage

I failed twice with the TWRP method, (I know there has been some successes posted in here with it though) the fastboot flash method worked for me first time