-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Dev: flash additional partitions #246
Conversation
@anon1892 I changed a few things and improved the layout in the app a bit. Most notably, the process now checks for the android version of the ROM you want to flash and only then decides if the selection for additional images should be displayed. What is missing now:
Please have a look and give it a test if you can/want 😊 Also, feel free to add a PR to this PR to improve it! |
Ok, will test it when I have time.
Maybe a button opening an info box?
As far I know, it's only needed for A13. So, no need for an additional config option? |
Great! Thanks a lot!
Yeah, I guess so. I will try to write a good text for it.
That's a good idea! I will think about a UI layout for that :) |
Without OFox for now? It will require more testing, because when OFox support will be added, we will need to test OFox AND TWRP just in case it breaks something, isn't it? For |
Why "recovery already flashed" and "bootloader already unlocked" toggles don't behave the same way? And I can't test properly, I have to make changes in device config, add #218, and maybe others things too... |
good point, actually, I guess they both should be only available after the device is detected. What do you think?
I understand and I'm sorry for the inconvenience. I would prefer not to push out releases with too many changes at the same time and also the OFox integration needs some more thought to make it future proof. Being able to flash additional partitions would be valuable immediately and would enable supporting more devices. So, I guess, we would add devices with TWRP support first to test flashing of additional partitions and then move on to add Ofox support. |
I would say the opposite, or move these buttons to the bottom (I read from top to bottom, so I click on buttons from top to bottom too, and I think a lot of users do the same)
Understandable! But we will need to add |
Hey @anon1892, I guess merged and integrated all the required parts for a first test. Let me know if it works for you and/or if something is missing! :) |
Hey, thanks a lot for testing and reporting this issue! It should be fixed and improved now! :) |
That was fast !!! Yes it works now |
Ok! I was writing this because adb behaves strangly, and on my phone, stop at 47% when sideload is finished...
Maybe show this button only in a “developer mode”? |
Ah yes, that's true. The installer on the PC reaches 100% at the end but on the phone it only gets to 47%...
Yeah, I need to prepare to move all "advanced features" to a developer or advanced mode. I'll try to simplify stuff again soon :) |
Ok, this is weird: My OnePlus One won't boot the twrp I got here (which worked all the time) and also won't flash it... I will try to investigate in the next few weeks, but I am also pretty busy atm... |
Thanks for testing. Then I will also do some more testing with older devices, maybe I find something :) |
So, I got to test with some old Samsung and Sony devices (so far I don't own a OnePlus device). And as far as I can tell everything seems to work as expected. |
Yes, I just reproduced the issue. The OAI log does not show any interesting or relevant information regarding the error - just the normal log...
But even after waiting minutes, nothing is happening on the OnePlus One side. - It seems like it freezes every time, as fastboot does not respond to fastboot commands anymore. |
I have a one plus one and faced the same behaviour on current stable 0.4.5 The step where we try to boot the recovery via fastboot just let it stuck like you described |
I also tried to boot twrp manually over cli, but nothing changes... |
And I assume there was no issue with version 0.4.4, right? So there must be a regression somewhere on the |
Nope same issue on 0.4.4 - I don't think that this is an issue with OAI, but rather with the devices itself... |
Hm, might be. Maybe it does not implement "wait for recovery" yet? 🤔 What happens if you boot to recovery manually and then run |
I can't even boot the recovery - that is the point: It worked perfectly fine weeks ago and suddenly I am only able to flash stock stuff and not even boot custom recoveries. The bootloader just freezes and becomes unavailable. |
I have the feeling, that there is some kind of limit reached / the recovery storage sector might be broken or something else... |
Hm, that's weird. I had a bit of a similar thing (for a samsung device) and just using a different usb-cable somehow seemed to fix it 🤷♂️ 🤔 but could also have been random...
Never heard of something like that (which does not necessarily means something). Booting the recovery leaves no real trace on the device. And if you can flash the stock recovery and image, then something seems to work still. Really interesting. 🤔 |
Tried another cable - no difference 😞 |
Can we move forward with this? I'm slowly wrapping up stuff for the new release. What can/should we do about the OnePlus issues? Somehow weird, that it comes up now. Can someone try with an older version of the installer? |
From my side you can merge...
I already tried it in an older version, in which it was working before. I will open an issue to continue with the problem... |
This PR is based on #220 (by @anon1892) and aims to integrate the code in the Installer.
fastboot_flash_recovery
andfastboot_reboot_recovery
(thanks to @anon1892)Other fixes & additions:
Todo:
adb reboot recovery
is not performed. Fix that.