NEO U22-XJ: 007 FW 20210923 OTA - Black screen on reboot

CybeRider

Trusted Helper
#61
I have tested this issue on several devices and can't replicate it,updated V003 to V007 via OTA,and tried V004 to V007 via OTA,turn-on ROOT,or Turn-off ROOT.Are there any special procedures or requirements?
Hi @MINIX - Nick,
It might be of interest to take into consideration what @Pingouin wrote in #21 above. The same exact thing that he reports happens when I try to replicate the situation. There is always a black screen lasting for some minutes in which I thought, for the first time, the box had stalled. Fortunately I resisted the urge to pull the power cord and so it progressed smoothly after what seemed like a long wait. I wonder if there might be some boxes in which this doesn't happen as for me it seems to be default for this update.
 
Last edited:

dak7385

Active member
#62
There is always a black screen lasting for some minutes in which I thought, for the first time, the box had stalled. Fortunately I resisted the urge to pull the power cord and so it progressed smoothly after what seemed like a long wait.
Mine did exactly the same, but I just waited until the light blue speckled screen appeared, which had been mentioned on previous official updates on the forum from Minix. And then all was good.
 
#63
I'm not sure if that's possible, but if Minix could keep a message on the screen while the box updates, that could help.
When one has a black screen, it's difficult to know whether it's because the device is sending a black screen, or whether the device isn't sending any signal at all!
I'm not an Android guru, but I presume that would mean needing the updating the bootloader (or recovery? Not sure which one installs the update!) to include such a message, if at all possible?
Looking at my Huawei phones and tablets, I'm pretty sure they keep you informed on screen at all times, so I've never been tempted to reboot them in the middle of an update.
 
#64
I have tested this issue on several devices and can't replicate it,updated V003 to V007 via OTA,and tried V004 to V007 via OTA,turn-on ROOT,or Turn-off ROOT.Are there any special procedures or requirements?
Hi Nick, thanks for looking at this issue. As I originally mentioned in post #1 of this thread, my screen went black and stayed black after I updated from V006A to V007 that you don't mention trying, see photo I took of the FOTA screen giving details at https://theminixforum.com/index.php...-screen-on-reboot.4168/#lg=post-35345&slide=0 . I have never touched the root switch, I have always used the box with only the FW supplied by Minix, and apps from the Google playstore and 'phase beam' wallpaper I downloaded from the internet. I mentioned that this wallpaper appeared very briefly for a fraction of a second with no app icons or anything else on it just before the screen went black. I waited some minutes after the screen went black before pulling the power cord and rebooting, its possible I did not wait long enough after the screen went black, it would be good as Pingouin suggested in #65 to have some indication the box is still rebooting other than a totally black screen for some minutes. I haven't done anything with my original U22-XJ with a black screen. I considered all the alternatives, but ended up buying a new second U22-XJ with V004 and am using that. I have never manually updated a Minix Android box, but can have a try to update my original U22-XJ sometime, would like to keep the data if at all possible, pusb87 mentioned this is possible in #55 if you 'select ONLY erase bootloader in the USB burn tool' which was news to me, thanks pusb87.
 
Last edited:

notrui

Trusted Helper
#65
but can have a try to update my original U22-XJ sometime, would like to keep the data if at all possible, pusb87 mentioned this is possible in #55 if you 'select ONLY erase bootloader in the USB burn tool' which was news to me, thanks pusb87.
In the future if you are going to try manual update i advice you:
-save to one external HDD your apps installed or to a NAS.
-yes you can use "only erase bootloader" but i advice you to leave USB burning tool (V.2.2.0) with default settings (Erase flash and erase bootloader).
-disable internet connection (From PC and minix), remove everything you don't need from the minix device (pen drive, etc) and flash the device (with the correct firmware).
-wait for the process to be complete with sucess
 
Last edited:
#66
In the future if you are going to try manual update i advice you:
-save to one external HDD your apps installed or to a NAS.
-yes you can use "only erase bootloader" but i advice you to leave USB burning tool (V.2.2.0) with default settings (Erase flash and erase bootloader).
-disable internet connection (From PC and minix), remove everything you don't need from the minix device (pen drive, etc) and flash the device (with the correct firmware).
-wait for the process to be complete with sucess
Thanks. Problem with this black screen issue is that I appear to have no access or any means of interacting with my U22-XJ that would enable me to remove anything to a external drive, as I mentioned in post #1, the,

'A3 air mouse pointer works, and long press on A3 red on/off button produces Power off/Sleep/Restart/Screenshot tab which works, but other buttons on A3 don't seem to work. Screen remains black'

all I have otherwise is a totally black screen, no access to the apps, file folders or anything like that.
 

notrui

Trusted Helper
#68
why ?
never had any issues doing this
It is my personal choice:
-With a clean ROM for feedback , tests and stability , etc

If something goes wrong i can identify more easiliy (and i don't need to reflash the ROM again).
In the past I had issues with only erase booloader.

It takes more work but i prefer.
 
#69
It is my personal choice:
-With a clean ROM for feedback , tests and stability , etc

If something goes wrong i can identify more easiliy (and i don't need to reflash the ROM again).
In the past I had issues with only erase booloader.

It takes more work but i prefer.
yes ... but in the meantime the Ota app no longer has the f007 update .... so I assume that the problem exists ..... what do you think?
 

CybeRider

Trusted Helper
#71
It is my personal choice:
-With a clean ROM for feedback , tests and stability , etc

If something goes wrong i can identify more easiliy (and i don't need to reflash the ROM again).
In the past I had issues with only erase booloader.

It takes more work but i prefer.
why ?
never had any issues doing this
I have to agree that is is better to do it with both options activated when you are doing a manual update. I had an issue in the past which had to do with regaining the ability to perform OTA updates. It was only solved after manually getting back two versions to the former one that had been OTA updated and then reinstalling the two next versions (the one I had, which had been manually installed, and only then OTA updating the one that had been most recently released).

My opinion ever since is that running USB burning tool (V.2.2.0) with the two options marked is the way to go for a proper update. (Of course all will be lost and will have to be reinstalled again, and that can be a pain. I personnaly have screen shots copied to a computer of the apps pages so I don't forget any. )

It is my feeling that running USB burning tool (V.2.2.0) with only the "erase bootloader" activated is great when you are reinstalling the same firmware version that you already had. And it is the only way to keep what you had in the internal disk, especially if you failed to back it up. And probably you will even be able to run it ever since with no problems what so ever, as the situation I experienced could be caused by something else or simply be the one in a million that required that solution.

I don't know if this is the most popular opinion, but is the one that also works for me.
 

dak7385

Active member
#72
I have to agree that is is better to do it with both options activated when you are doing a manual update. I had an issue in the past which had to do with regaining the ability to perform OTA updates. It was only solved after manually getting back two versions to the former one that had been OTA updated and then reinstalling the two next versions (the one I had, which had been manually installed, and only then OTA updating the one that had been most recently released).

My opinion ever since is that running USB burning tool (V.2.2.0) with the two options marked is the way to go for a proper update. (Of course all will be lost and will have to be reinstalled again, and that can be a pain. I personnaly have screen shots copied to a computer of the apps pages so I don't forget any. )

It is my feeling that running USB burning tool (V.2.2.0) with only the "erase bootloader" activated is great when you are reinstalling the same firmware version that you already had. And it is the only way to keep what you had in the internal disk, especially if you failed to back it up. And proba

My opinion ever since is that running USB burning tool (V.2.2.0) with the two options marked is the way to go for a proper update. (Of course all will be lost and will have to be reinstalled again, and that can be a pain. I personnaly have screen shots copied to a computer of the apps pages so I don't forget any. )

It is my feeling that running USB burning tool (V.2.2.0) with only the "erase bootloader" activated is great when you are reinstalling the same firmware version that you already had. And it is the only way to keep what you had in the internal disk, especially if you failed to back it up. And probably you will even be able to run it ever since with no problems what so ever, as the situation I experienced could be caused by something else or simply be the one in a million that required that solution.

I don't know if this is the most popular opinion, but is the one that also works for me.
Thanks for explaining that. I was trying to understand the difference and what happened by choosing one or the other methods of reflashing.
 

Website:http://minix.com.hk
Facebook:  facebook.com/minixtech
Telegram Channel: t.me/minix_channel
Telegram Group:    t.me/minix_group

Top