[Q] Flash via Fastboot - Android One (First-Generation) Cross-Device Genera

Hey guys.
I have this little problem with my Android One. I can't flash 'SYSTEM' via fastboot.
har****@har****:~ fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
OKAY [ 0.702s]
sending sparse 'system' (131071 KB)...
OKAY [ 4.725s]
writing 'system'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 5.431s
har****@har****:~
Click to expand...
Click to collapse
I got this error while flashing Ubuntu Touch (Which I built), Android 5.0 (Which, again, I built) and also AOKP's system.img
Any solutions to this?

rhar**** said:
Hey guys.
I have this little problem with my Android One. I can't flash 'SYSTEM' via fastboot.
I got this error while flashing Ubuntu Touch (Which I built), Android 5.0 (Which, again, I built) and also AOKP's system.img
Any solutions to this?
Click to expand...
Click to collapse
Hey ,
I am facing the same problem after building aosp 4.4.4
Did you find a solution ?

joshuab227 said:
Hey ,
I am facing the same problem after building aosp 4.4.4
Did you find a solution ?
Click to expand...
Click to collapse
Not yet

rhar**** said:
Not yet
Click to expand...
Click to collapse
I was unable to flash it via fastboot but could flash it by creating an ota zip.

joshuab227 said:
I was unable to flash it via fastboot but could flash it by creating an ota zip.
Click to expand...
Click to collapse
Same here.
But many a times you need to flash from fastboot. Flashing zip isn't practical when you are making a new os

BTW I compiled resurrection remix lp with your device tree @rhar****, when I try to flash it fails to mount system. Any clue what I can do?
Sent from my Android One using XDA Free mobile app

akhil1999 said:
BTW I compiled resurrection remix lp without your device tree @rhar****, when I try to flash it fails to mount system. Any clue what I can do?
Sent from my Android One using XDA Free mobile app
Click to expand...
Click to collapse
You need to take a log of what's the problem and debug it. Its not the device tree thing, though

https://docs.google.com/file/d/0B1MuHk_wIzdxUEZpdnozVUMtM0E/edit?usp=docslist_api
That's my recovery.log
Please help if you can.
Thanks.

akhil1999 said:
https://docs.google.com/file/d/0B1MuHk_wIzdxUEZpdnozVUMtM0E/edit?usp=docslist_api
That's my recovery.log
Please help if you can.
Thanks.
Click to expand...
Click to collapse
Better talk in pm

Related

[Q] Stock Recovery Partition Missing?

Just curious, does anyone have a dump of the recovery partition for the Dev Edition? It looks like from a bit of reading is that the recovery partition doesn't seem to be present.
I am unable to use recovery mode properly since it saids invalid operation when I do apply from SD, storage or cache, followed by the phone automatically restarting.
Has anyone else noticed this? I wonder if the unlocked 32 GB versions is unaffected.
try to reflash the recovery, the partitions should be the same as the original One
I tried to do that by using the RUU and using the zip, but it did not bring it back.
Is there a way to get the recovery image itself? I tried to extract the zip but it looked like it's encrypted as I cannot do so.
Looks like one mike1986 mentioned it's missing as well.
mike1986. said:
1. Well, I decided not to mention some things to avoid confusion. At the moment unlocking bootloader removes content of /data/preload partition, so indeed, installing OTA will fail. But I truly hope that HTC will fix it at some point and unlocking bootloader won't cause some stock apps to be missing.
2. Which procedure?
Click to expand...
Click to collapse
Sango2 said:
I tried to do that by using the RUU and using the zip, but it did not bring it back.
Is there a way to get the recovery image itself? I tried to extract the zip but it looked like it's encrypted as I cannot do so.
Looks like one mike1986 mentioned it's missing as well.
Click to expand...
Click to collapse
if you can point me where the RUU for your dev edition is i can extract the recovery.img for you
matt95 said:
if you can point me where the RUU for your dev edition is i can extract the recovery.img for you
Click to expand...
Click to collapse
Great, thanks a lot.
Two places you can get it from
http://forum.xda-developers.com/showthread.php?p=39588860 (BrightstarUS_WWE which is Developer)
or directly from HTCdev
http://www.htcdev.com/devcenter/downloads
Sango2 said:
Great, thanks a lot.
Two places you can get it from
http://forum.xda-developers.com/showthread.php?p=39588860 (BrightstarUS_WWE which is Developer)
or directly from HTCdev
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
ok, i'm downloading!
very very slow D:
matt95 said:
ok, i'm downloading!
very very slow D:
Click to expand...
Click to collapse
No worries, I'll be back on tonight since got some meetings to attend in the office. Lets see what you can discover.
Thanks!
ok, iside of it i found this recovery file! try to flash it using
Code:
fastboot flash recovery recovery_signed.img
Download
matt95 said:
ok, iside of it i found this recovery file! try to flash it using
Code:
fastboot flash recovery recovery_signed.img
Download
Click to expand...
Click to collapse
Tried it but for some reason I get this.
Code:
recovery recovery_signed.img
sending 'recovery' (9590 KB)...
OKAY [ 1.233s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.376s
Sango2 said:
Tried it but for some reason I get this.
Code:
recovery recovery_signed.img
sending 'recovery' (9590 KB)...
OKAY [ 1.233s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.376s
Click to expand...
Click to collapse
as i though, mmmhh, unzipping the file breaks the signature.... well then you need to download a stock nandroid backup and inside of it you will fina a recovery.zip... just flash it and you're ready to go
matt95 said:
as i though, mmmhh, unzipping the file breaks the signature.... well then you need to download a stock nandroid backup and inside of it you will fina a recovery.zip... just flash it and you're ready to go
Click to expand...
Click to collapse
Hmm, I'm beginning to wonder if the stock recovery is suppose to work like that, where if I try to apply storage, sd card, or cache it saids invalid operation and reboot. The reason is, a new HTC One S my relative got she her phone is being replaced for free under warranty... I go to the recovery and do those certain the apply stuff, it also saids invalid operation out and restarts!
I find this a bit interesting on my HTC One when I go to the recovery and wondering the failed mount SD card messages is normal.
Try this -> http://vps.rana.sg/HTC_ONE/individual_files/recovery.emmc.win
fastboot erase cache
fastboot flash recovery recovery.emmc.win
v-b-n said:
Try this -> http://vps.rana.sg/HTC_ONE/individual_files/recovery.emmc.win
fastboot erase cache
fastboot flash recovery recovery.emmc.win
Click to expand...
Click to collapse
I get this error.
Forbidden
You don't have permission to access /HTC_ONE/individual_files/recovery.emmc.win on this server.
Click to expand...
Click to collapse
Sango2 said:
I get this error.
Click to expand...
Click to collapse
Oops ... try now
v-b-n said:
Oops ... try now
Click to expand...
Click to collapse
I don't mean to hijack this thread but I tried flashing it on my HTC One and I received a signature verify fail...
Code:
sending 'recovery' (16383 KB)...
OKAY [ 1.921s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.876s
I don't get it why signature check is happening... Is the bootloader in unlock status and which custom recovery aren't of trying to overwrite?
Sent from my HTC One using xda premium
v-b-n said:
I don't get it why signature check is happening... Is the bootloader in unlock status and which custom recovery aren't of trying to overwrite?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
i'm wondering that too, but is that a recovery taken from the RUU.zip?
matt95 said:
i'm wondering that too, but is that a recovery taken from the RUU.zip?
Click to expand...
Click to collapse
It's A twrp backup which is flashable using fastboot... I have done it so many times, hope people are flashing the fastboot way?
Sent from my HTC One using xda premium
The only time bootloader is going to Sig check a recovery partition is if he is relocked. He said he used the ruu a couple times so he is still relocked.
v-b-n said:
It's A twrp backup which is flashable using fastboot... I have done it so many times, hope people are flashing the fastboot way?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
... you mean taken from the TWRP backup?

how to root

hey is it possible to root the phone without a developer rom?
Flo5190 said:
hey is it possible to root the phone without a developer rom?
Click to expand...
Click to collapse
Yup. Flash TWRP from here https://mega.co.nz/#!d0cFFCLZ!tZN38HAzpIKQXbsRkwVJBkyGr5f1OUPaIZkxt3Bfiak
and then flash supersu.zip
Kahun said:
Yup. Flash TWRP from here https://mega.co.nz/#!d0cFFCLZ!tZN38HAzpIKQXbsRkwVJBkyGr5f1OUPaIZkxt3Bfiak
and then flash supersu.zip
Click to expand...
Click to collapse
Hi, how to go to TWRP to flash supersu.zip?
vietvp said:
Hi, how to go to TWRP to flash supersu.zip?
Click to expand...
Click to collapse
Go into fast boot and use fastboot flash recovery.img
Kahun said:
Go into fast boot and use fastboot flash recovery.img
Click to expand...
Click to collapse
My rom is stable V6.5.10, i have flashed TWRP successful, but goto Updater -> Reboot to recovery mode and phone still boot to Mi recovery, not TWRP.
D:\Minimal ADB and Fastboot>fastboot flash recovery twrp_recovery_for_xiaomi_leo_en.img
target reported max download size of 1073741824 bytes
sending 'recovery' (46404 KB)...
OKAY [ 1.028s]
writing 'recovery'...
OKAY [ 0.367s]
finished. total time: 1.400s

STOCK recovery and kernel pack from EMUI 3.0 / 3.1 ROM's

Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S:
L10-B602
L00-B607
L07-B607
L10-B609
L10-B613
L10-B621
L10-B805
L10-B813
L10-B815
L10-B817
L10-B830
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Thanks for sharing man. I appreciate it!
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Thanks Ziolek. Any possibility to have the B8xx stock update.app?
v11lemans said:
Thanks Ziolek. Any possibility to have the B8xx stock update.app?
Click to expand...
Click to collapse
And the B8xx stock flashable file? :victory:
And so we can flash any recovery of the B609 to get the stock recovery? Right?
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Dude, you have to check your files.... I am trying to flash the B813 and B805 recovery but both dont boot at all.... Led flashing red and blue and then i get the white boot failed screen
Flashed with flashify and rashr
I used that files. Everything was ok. But I don't us flashify. Only fastboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
I used that files. Everything was ok. But I don't us flashify. Only fastboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
Hmm weird... Maybe flashify and rashr dont work on lollipop... Have to get to a pc nearby to flash.
Sent from my HTC One using XDA Free mobile app
its the peanut said:
Hmm weird... Maybe flashify and rashr dont work on lollipop... Have to get to a pc nearby to flash.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I have tested B813 kernel and recovery now and it is working properly.
I Flashed it by fastboot and system booting.
I haven't now possibility to checking B805 files because I am on B813 system now.
Maybe try to re-downloading package.
Does anyone have any idea if it's possible to flash a recovery without fastboot even when you can't boot into the os? Right now I can't do anything with my phone...
My pc doesn't recognise my phone in fastboot mode but, it does recognise adb but, only when I try to flash something (hold vol-+ and put in usb cable). If anyone is able to help me please say it...I've got a thread named phone bricked good somewhere on this forum (ascend p7 general).
Thanks in advance and sorry for the trouble
sincerly,
Jules
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Do you have recovery stock of b830?
Updated
target reported max download size of 536870912 bytes
sending 'boot' (8026 KB)...
OKAY [ 0.319s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.329s
whats problem here
abumaha said:
target reported max download size of 536870912 bytes
sending 'boot' (8026 KB)...
OKAY [ 0.319s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.329s
whats problem here
Click to expand...
Click to collapse
Google it

[Q] Unable to flash factory images

I only started trying this since last night but I am unable to flash factory images. I tried the 5.1.1 non-tmobile image, as well as today's 6.0 release image. (Hardware: Macbook Pro w/ OS 10.11 El Capitan)
I've tried both flash-all.sh as well as fastboot update and both end up with the same error message:
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.327s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.726s]
finished. total time: 1.053s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 3.616s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.532s]
finished. total time: 5.149s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(3602,0xa2ed1000) malloc: *** mach_vm_map(size=2094395392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2092300200 bytes
error: update package missing system.img
Looking at the image-shamu-mra58k.zip file, it does not contain any .sig files. Only userdata.img, system.img, recovery.img, cache.img, boot.img and android-info.txt.
Any idea what's going on and how to fix it?
Unlock the bootloader?
MrBrady said:
I only started trying this since last night but I am unable to flash factory images. I tried the 5.1.1 non-tmobile image, as well as today's 6.0 release image. (Hardware: Macbook Pro w/ OS 10.11 El Capitan)
I've tried both flash-all.sh as well as fastboot update and both end up with the same error message:
Looking at the image-shamu-mra58k.zip file, it does not contain any .sig files. Only userdata.img, system.img, recovery.img, cache.img, boot.img and android-info.txt.
Any idea what's going on and how to fix it?
Click to expand...
Click to collapse
Just manually flash the images.
iRub1Out said:
Unlock the bootloader?
Click to expand...
Click to collapse
Bootloader is unlocked and I am running TWRP recovery. Does it need to be stock recovery and locked bootloader to flash the factory images?
danarama said:
Just manually flash the images.
Click to expand...
Click to collapse
Like this?
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
yes, actually, exactly like that.
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
530farm said:
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Click to expand...
Click to collapse
I get a dead Android with a red triangle when trying to boot into recovery. It seems my TWRP got toasted somehow. However I do not receive any corrupt notice when booting the device normally.
I performed a fastboot flash of TWRP 2.8.7.1 and on first boot, TWRP gave a warning where I had to accept that it was OK to modify the system. I have never seen that before. After installing TWRP I do get the corrupt device message upon boot.
useranonymous said:
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
Click to expand...
Click to collapse
Is there one available for Mac?
useranonymous said:
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
Click to expand...
Click to collapse
If I used Nexus Toolkit what should i choose to flashed it. Fastboot: System?
MrBrady said:
Is there one available for Mac?
Click to expand...
Click to collapse
You can try this one.
http://forum.xda-developers.com/nexus-6/development/toolkit-nexus-6-one-click-mac-toolkit-t2956434
---------- Post added at 06:48 PM ---------- Previous post was at 06:42 PM ----------
chipis said:
If I used Nexus Toolkit what should i choose to flashed it. Fastboot: System?
Click to expand...
Click to collapse
I used the WUG toolkit and used flash Stock +Unroot with the Other/Browse option for picking the downloaded img.
I also checked "Force Flash Mode" and let the tool run through the script.
useranonymous said:
You can try this one.
http://forum.xda-developers.com/nexus-6/development/toolkit-nexus-6-one-click-mac-toolkit-t2956434
---------- Post added at 06:48 PM ---------- Previous post was at 06:42 PM ----------
I used the WUG toolkit and used flash Stock +Unroot with the Other/Browse option for picking the downloaded img.
I also checked "Force Flash Mode" and let the tool run through the script.
Click to expand...
Click to collapse
Sorry iam noob to this. So i have a custom rom. should go and flash a stock.?
Because ones i press what you said it jumps to look for image but it dont find anything
chipis said:
Sorry iam noob to this. So i have a custom rom. should go and flash a stock.?
Because ones i press what you said it jumps to look for image but it dont find anything
Click to expand...
Click to collapse
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
useranonymous said:
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
Click to expand...
Click to collapse
Jisus i feel dumm, ok i have flashed the image before M, Because i was on the LVY48E
Sorry i coming from samsung device. Nexus is a little different.
Now I just download the M Where should go To flashed what just downloaded using the Nexus Root Tool Kit?
lose root if flash M ??
useranonymous said:
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
Click to expand...
Click to collapse
If I manually flash M, I'll lose root ? Oh, say it isn't so .
530farm said:
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Click to expand...
Click to collapse
Can you boot into the system? My nexus 6 will just turns itself off after the message
redlee90 said:
Can you boot into the system? My nexus 6 will just turns itself off after the message
Click to expand...
Click to collapse
Yes, it boots fine.
I can even get root by flashing an M-based kernel, then the SuperSU 2.49 zip. However when I flash apps that install as System Apps (like ViPER4Android), they don't seem to install. It's almost like TWRP doesn't have root access.
ok finally flash the image M Using Nexus Root ToolKIt
Don't use toolkits if you don't know what you're doing. Use manual fastboot steps.
danarama said:
Don't use toolkits if you don't know what you're doing. Use manual fastboot steps.
Click to expand...
Click to collapse
Good point.
Have a good guide to do this for us noobs?

Can't flash vendor.img but i have TWRP [What to do ?]

Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??

Categories

Resources