Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootloader seems to not erase? #5

Open
ghost opened this issue Feb 12, 2019 · 0 comments
Open

Bootloader seems to not erase? #5

ghost opened this issue Feb 12, 2019 · 0 comments

Comments

@ghost
Copy link

ghost commented Feb 12, 2019

I am trying to flash customised 7.1 rom. When I use --destroy to erase bootloader before flashing everything seems fine message says: "it is erased nothing to do more". Whole flashing process goes without error. However when device resets it stays stuck on powerup logo (when I issue command --destroy in this state (still connected to device) it again says it was successfull, powerup logo disappears to black screen and it seems like bootloader was erased. However rom never boots. I used the same command few days ago and rom booted. I haven't changed the rom since, it stays on external drive. But I can successfully flash other rom (6.0). I don't know what the problem is it seems that the bootloader of 6.0 rom is never erased and stays behind even though the tool says it was erased. Is it possible? I always first --destroy than flash with "all parts, --wipe". What can I do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants