Related
Hi there! I have been stumped for the past 18 hours trying to fix my phone, and I decided to come to the people who actually know what they are doing. I had Cyanogenmod installed on my phone, and I wanted it gone. I have somewhat forgot the steps I have taken in between.
I am at the point where I have the following tags on my H-Boot (Version 1.56) Tampered & Re-Locked. I have TWRP installed, using sideloader always gives me a error (executing updater binary in zip). Trying to mount to sdcard, gives me a error (unable to mount /data/). Using fastboot to flash with either a recovery img or the rom gives me a error (signature verify error).
Any help is appreciated. I can Skype Screen-share and call with people, if it would speed up the process, if you would be willing to help with that, please drop me a PM with your Skype name. All and any help is appreciated. Cheers.
Unlock your bootloader at HTC Dev, that's why you cant flash recovery, and certainly wont be able to flash any ROM's with it locked.
ps. not bricked at all.
Seanie280672 said:
Unlock your bootloader at HTC Dev, that's why you cant flash recovery, and certainly wont be able to flash any ROM's with it locked.
ps. not bricked at all.
Click to expand...
Click to collapse
Unlocked my bootloader, installed TWRP, however I am back to this rather annoying 'error: device not found' I fixed it before by killing and re-starting the server, however sideload still giving me that. Any help?
Edit: Got that working, however sideload is giving me assert failed: file_getprop and Error executing updated binary in zip.
Seanie280672 said:
Unlock your bootloader at HTC Dev, that's why you cant flash recovery, and certainly wont be able to flash any ROM's with it locked.
ps. not bricked at all.
Click to expand...
Click to collapse
Casper001 said:
Unlocked my bootloader, installed TWRP, however I am back to this rather annoying 'error: device not found' I fixed it before by killing and re-starting the server, however sideload still giving me that. Any help?
Edit: Got that working, however sideload is giving me assert failed: file_getprop and Error executing updated binary in zip.
Click to expand...
Click to collapse
Update, I tried fastboot update, but I am getting does not contain android-info & product.txt. Any help?
what exactly are you trying to do and what are you trying to flash ?
Can you get into recovery ?
Seanie280672 said:
what exactly are you trying to do and what are you trying to flash ?
Can you get into recovery ?
Click to expand...
Click to collapse
I am trying to get my stock sense back. I have pushed the ROM of it onto my /data/ right now. I can access recovery. I am guessing on TWRP I just install now? However, I will wait for a reply.
Casper001 said:
I am trying to get my stock sense back. I have pushed the ROM of it onto my /data/ right now. I can access recovery. I am guessing on TWRP I just install now? However, I will wait for a reply.
Click to expand...
Click to collapse
Ok just out of interest, which rom did you push ?
Seanie280672 said:
Ok just out of interest, which rom did you push ?
Click to expand...
Click to collapse
The full name of the ZIP I downloaded was:
Code:
OTA_M7_UL_K44_SENSE55_MR_Vodafone_UK_4.19.161.11-3.63.161.6_release_356881mwn487m942rk64ep
It's the one I got told for my phone, as I am on Vodafone and it matches with my details.
That wont work, its not a zip, that's why your having problems, its the official RUU
I have a backup of the Vodafone original rom for your device, I will PM you a link, but first will you enter your recovery and backup your current rom please, the reason I ask you to do this is because by doing a backup, TWRP will automatically creat a couple of folders where you will need to put the backup I give you.
Seanie280672 said:
That wont work, its not a zip, that's why your having problems, its the official RUU
I have a backup of the Vodafone original rom for your device, I will PM you a link, but first will you enter your recovery and backup your current rom please, the reason I ask you to do this is because by doing a backup, TWRP will automatically creat a couple of folders where you will need to put the backup I give you.
Click to expand...
Click to collapse
Cheers dude. I have backed up every folder on TWRP.
unzip the file I give you and extract it somewhere where you can find it all like on your desktop.
flash the recovery included in the zip, just incase of compatibility issues, its still TWRP, just a different version.
Copy backup folder and its contents to your internal phone memory - TWRP - BACKUPS - (folder named device serial number) - place the folder with the backup here.
Enter recovery and flash it.
---------- Post added at 09:00 PM ---------- Previous post was at 08:56 PM ----------
2 mins, just uploading it to my google drive
Seanie280672 said:
unzip the file I give you and extract it somewhere where you can find it all like on your desktop.
flash the recovery included in the zip, just incase of compatibility issues, its still TWRP, just a different version.
Copy backup folder and its contents to your internal phone memory - TWRP - BACKUPS - (folder named device serial number) - place the folder with the backup here.
Enter recovery and flash it.
---------- Post added at 09:00 PM ---------- Previous post was at 08:56 PM ----------
2 mins, just uploading it to my google drive
Click to expand...
Click to collapse
Will do, cheers again mate.
PM Sent
Seanie280672 said:
PM Sent
Click to expand...
Click to collapse
Downloading right now, 8 mins left on the download, and unknown on the extraction (this old laptop can be a little iffy at times), however thank you a ton mate, and it seems fairly simple from now I'll let you know how it gets on!
I've a stock xt1052 with 4.4.4, root and twrp 2.8.1.0 and whrn i try to flash some roms (like aicp or cm) , the process failed with response of recovery "E: error executing updater binary in zip '..path of file..'" ...any idea?
No one?!
No issues here flashing cm with TWRP 2.8.1.0
Maybe a bad download...
Verify md5sum?
I installed TWRP on my XT1052 moto x just last week, had some issues with flashing TWRP as well.
If the MD5 check is fine, you can try changing USB ports (sounds silly but it worked for me, found it in another xda post but had something to do with fastboot not playing well with some USB ports).
what do you mean? How to do the md5sum check?
interista4e said:
what do you mean? How to do the md5sum check?
Click to expand...
Click to collapse
I use root explorer. Long press the zip and select properties. At the bottom it will calculate your md5sums. Verify that matches to the download md5sum to verify it is a good download. Most all download pages have a md5sum listed to compare.
Travisdroidx2 said:
I use root explorer. Long press the zip and select properties. At the bottom it will calculate your md5sums. Verify that matches to the download md5sum to verify it is a good download. Mosf all download pages have a md5sum listed to compare.
Click to expand...
Click to collapse
The result is that the md5 is the same of the download page
interista4e said:
The result is that the md5 is the same of the download page
Click to expand...
Click to collapse
Then you have a good download
What is the sequence of your flashing.
When I flash aosp Roms I:
- wipe > factory reset only. I never wipe system separately.
- flash aosp ROM of choice
- flash gapps
- reboot system.
And no issues here ever flashing aosp Roms.
Hope this helps.
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
Also which aosp ROM are you trying to flash?
Wipe> swipe factory> then flash latest aicp release 6.0 and gapps together> error
Have you tried like cm11 or slimkat? Both of those boot fine for me. Never tried the ROM you are having problems with. The download files for aosp and moto x are now labeled ghost.
---------- Post added at 05:12 PM ---------- Previous post was at 05:04 PM ----------
interista4e said:
Wipe> swipe factory> then flash latest aicp release 6.0 and gapps together> error
Click to expand...
Click to collapse
Link to the ROM you are trying to flash? You are flashing a aosp ROM for "ghost" which is moto X correct?
http://forum.xda-developers.com/moto-x/development/rom-aicpmoto-x-unifiedmsm8960dt-t2834400 this....rom is the first of yhe download page...the release
interista4e said:
http://forum.xda-developers.com/moto-x/development/rom-aicpmoto-x-unifiedmsm8960dt-t2834400 this....rom is the first of yhe download page...the release
Click to expand...
Click to collapse
That is your problem! You need "ghost" build. That is why it is failing. The one you are trying is old. Try CM11 bet it boots fine.
Ok, i'm stupid u.u but i met the same problem with the same method , flashing the official cm11 nightly 31/10....and it's ghost
interista4e said:
Ok, i'm stupid u.u but i met the same problem with the same method , flashing the official cm11 nightly 31/10....and it's ghost
Click to expand...
Click to collapse
Okay I am at a lost then if CM is giving you the same issue. Does your error or problem look lime this post? http://forum.xda-developers.com/moto-x/general/error-flashing-cm-based-roms-moto-x-t2915380
Travisdroidx2 said:
Okay I am at a lost then if CM is giving you the same issue. Does your error or problem look lime this post? http://forum.xda-developers.com/moto-x/general/error-flashing-cm-based-roms-moto-x-t2915380
Click to expand...
Click to collapse
No, it's similar to this https://lh4.googleusercontent.com/p...sDHYjeW8Edzcn0hldZbskA_hIQfQ6d5g=w384-h682-nc
This....i tried official pacman and same error....with slimkat , it works
interista4e said:
This....i tried official pacman and same error....with slimkat , it works
Click to expand...
Click to collapse
Hey.. I got same error on TWRP 2.8.1.0 with CrDroid ghost rom!! You got any solution yet??
OJ said:
Hey.. I got same error on TWRP 2.8.1.0 with CrDroid ghost rom!! You got any solution yet??
Click to expand...
Click to collapse
The problem is solved with the link of travisdroidx2, read and try, with me it work
Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.
@ayeitschris, I have the same problem my friend. Has anyone figured a way yet?
Same issue.
Seems like other note 4 users are having the same issues as well:
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-x-teamwin-t2956011/page56
yeah it will soft brick your recovery and you will have to odin 2.8.7.0 .
There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well
marseillesw said:
There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well
Click to expand...
Click to collapse
link?
marseillesw said:
There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well
Click to expand...
Click to collapse
Where is it?
Just flash it with the rashr app. U don't have to use odin when you have an existing recovery. Just flash over it via the app
---------- Post added at 02:56 AM ---------- Previous post was at 02:53 AM ----------
ayeitschris said:
Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.
Click to expand...
Click to collapse
I also have a T-Mobile note 4 and the recovery flashed perfectly. After you odin the first recovery you never have to use it again. Just use the rashr flashing app and you will never have one problem. The only time you will need odin is if you are going from twrp to cwm
---------- Post added at 02:57 AM ---------- Previous post was at 02:56 AM ----------
ayeitschris said:
Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.
Click to expand...
Click to collapse
Also do not flash a recovery update from your recovery
I have tried flashing it using odin, both stock and custom rom, as well as TWRP manager. 3.0.0 doesn't work. If I flash back to 2.8.7, all is fine. Apparently 3.0.0 doesn't work for the SM-N910T (T-Mobile) version. If anyone has had success with this model, please include links and detailed instructions as to how you successfully upgraded.
http://forum.xda-developers.com/showthread.php?p=65242953
---------- Post added at 09:55 PM ---------- Previous post was at 09:55 PM ----------
Hell-Razor said:
link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=65242953
Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:
Which firmware you had before brick?
MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?
MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly
70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.
This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).
You still need help?
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.
MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot
:good:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again