Database Users

Bootloop

Hi
I have an HTC Legend, but it's so buged
When i try to turn it on, it has to be connected to a cable, or else it goes into bootloop.
I've tried to make a factory reset, tried to install a different RUU, tried to downgrade it, but the adb shows no devices.
I've run out of ideas, so please help me

Somehow I managed to get the same issue. It goes into bootloop unless it's connected to a pc... I already went back to the stock 2.2 rom and deleted everything but nothing changed.
Funny thing is that after I got this problem I first installed the old 1.31 rom and that one worked without the usb cable. The 2.05 to. But as soon as I installed the 3.14 it started again with the bootloop thing...
Did you find any solutions?

Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)

CrWEE said:
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
Click to expand...
Click to collapse
What exactly means unbricking the phone?
I got simillar problems: since CM7 final I have bootloops when my phone isn't connected to power. Also I can't mount the sd card from a computer (when I press the button on the phone it works for like 5seconds and then unmounts again).
I already tried downgrading again to CM7 RC4 and other versions(I always wiped before), but the problem persists. Also upgrading to another radio version didn't work .

virus54 said:
I have this problem too
but i found one way to stop this rebot loop util u reboot your phone again...
enter into recovery mode and via adb write the command
adb devices
Click to expand...
Click to collapse
now press volume up and power button(when you see black screen with phone)
press on reboot system now and it will work for you for one time
each reboot you have to follow those steps
Click to expand...
Click to collapse
after this do a usb brick to use your usb http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/

I had exactly the same problem, the USB unbrick linked to above solved the problem. If you need the image hex edited for you give me a shout

[HELP] Rikomagic MG802 III dead after scaling video to 100%

Hello!
I turned on my MK802III and went to: Settings -> Video -> Scaling options -> 100%, and the screen started showing some odd pixel lines, mouse and keyboard stopped responding. After a few minutes, I unplugged the device, and now it just won't boot.
Now, the blue led turns ON and the TV recognizes that there is a signal, but goes to EnergySaving mode, and absolutely nothing else happens.
Any ideas? There is not much information around the internet about this.
Cheers!
PS: It was the device first boot! I had just received it.7
__________
UPDATE:
I guess I might have reached a conclusion...I think that the device might be boot looping. So I googled about how to restore/update firmware, but a needed a way to do this without having access to any of the device's UI. So I found a recovery method by short circuit at Armtvtech and there is also OFFICIAL information about this.
After downloading everything needed, I proceeded to short circuit the device. Everything ended up OK: drivers installed successfully, Rikomagic's tool detects the device, BUT after chosing the .img from Rikomagic's files and clicking 'update', the tool returns an error.
SCREENSHOT
Now I'm stuck here...can someone please help?

Hmm. Just got one myself Google rikomagic forum there is a sub forum with ROM list thread. Most roms include flasher im using finless 1.7a. you can reflash nand from windows. Unless was a hardware damage?
There's a reset button same side as USB otg. You have to have flasher prog on PC running and hold in reset while device connects like 10 secounds . install driver rinse and repeat run flasher
Sent from my Nexus 4 using XDA Premium HD app

Nanopane said:
Hello!
I turned on my MK802III and went to: Settings -> Video -> Scaling options -> 100%, and the screen started showing some odd pixel lines, mouse and keyboard stopped responding. After a few minutes, I unplugged the device, and now it just won't boot.
Now, the blue led turns ON and the TV recognizes that there is a signal, but goes to EnergySaving mode, and absolutely nothing else happens.
Any ideas? There is not much information around the internet about this.
Cheers!
PS: It was the device first boot! I had just received it.7
__________
UPDATE:
I guess I might have reached a conclusion...I think that the device might be boot looping. So I googled about how to restore/update firmware, but a needed a way to do this without having access to any of the device's UI. So I found a recovery method by short circuit at Armtvtech and there is also OFFICIAL information about this.
After downloading everything needed, I proceeded to short circuit the device. Everything ended up OK: drivers installed successfully, Rikomagic's tool detects the device, BUT after chosing the .img from Rikomagic's files and clicking 'update', the tool returns an error.
SCREENSHOT
Now I'm stuck here...can someone please help?
Click to expand...
Click to collapse
Could it be possible you are useing wrong version of the rockchip flash tool? The version you are useing may see the device. But wont flash. Try different one for your version of windblows and the device itself. Good luck.
Sent from my A200 using xda app-developers app

[Q] Bell D803 constant re-boot

A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!

Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.​
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"​
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next

I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...

do you have nandroid backup from previous rom?

I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.

or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497

zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?

I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?

asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.

I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?

Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803

Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)

natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.

ALL FIXED UP
WORKING 110%
:good:

natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.

zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?

natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:

zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?

natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.

zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!

cm 12.1 rom is fine but "System UI has crashed" ;-;

My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS

wifiwitch987 said:
My issue is a little strange but please bare with me.
I have CM 12.1 installed and after the boot up animation and arriving at the home screen I am hit with a "Unfortunately System UI has crashed." This is because I was trying out different CM Themes I was downloading from the play store. Most of them worked fine but one of them just messed everything up and this happened ::crying:
Complications
1. According to my research this issue could be easily resolved with on other android devices that actually have Power and Volume Buttons to enter the Recovery mode upon boot up but as you guys know the MOJO does not.
2. i cannot use my windows 10 pc to force the MOJO to recovery mode because my PC actually has an issue of its own right now where everytime I restart it, it wont boot back up until like the next day after all the power has drained out of it so I can actually never turn it off. And because of this I cannot do the thing where I have to restart my Windows 10 pc to disable driver signature verification otherwise I could use my PC to fix it.
Everytime before when I flashed roms back and forth from stock and Cm 12.1 I didnt use a PC I just used the MOJO itself.
I do have a physical keyboartd in my arsenal though so if there is a way to force the MOJO into recovery upon bootup with a certain Key combination I dont know about it. It's really crazy to believe that changing the CM themes is actually what screwed my MOJO rather than all the times before I've done so much more risky things on it.
Anyway if you guys can help me I would appreciate it. If not I just am going to cry myself to sleep. My email is [email protected] if you want to get in touch with me if you cant on here. THANKS
Click to expand...
Click to collapse
I think first I'd replace the PC. If that's not practical, try to boot it to this .iso once you've burned it to CD:
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Download the recovery.img to root's home, connect to the MOJO and turn it on, open a terminal and issue:
# fastboot -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
Should boot the MOJO into the recovery. If you can't get your PC to boot properly I think you're OOL. You might look into getting a used PC, one that's out-of-date or simply has a bad (or no) HDD, that you can pick up cheap, and use this simple Linux distro (Puppy Linux it is, with fastboot and adb binaries installed by me) for an OS. But be careful, Linux is addictive, and you may find yourself in the same predicament as I am: losing patience with the bloated domineering Windows OS.

Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude

wifiwitch987 said:
Hi thank you for the response. Replacing my PC is on my list but it is also easy to just go on without turning it on but i look to renew ym warranty with Alienware and having them fix or replace it, even though they should do it for free because it seem to be an issue alot of people are having with the early Alienware Alphas.
Anyways my PC is an alienware Alpha it doesnt have a disk drive. Can I just put this .iso on a usb flash drive instead of a cd-rom ? If I can do I have to format the flash drive to a certain format ?
Thanks dude
Click to expand...
Click to collapse
You can flash this (or most other linux live-CD .iso files) to a USB drive with a utility called Unetbootin. IIRC it's available for Windows, Mac, or Linux. I have no idea whether your Alpha is capable of booting to it, though. Any chance of borrowing another PC, maybe one a bit more traditional? Your little brother's old slow laptop maybe? FWIW I just finally managed to get fastboot and adb working on a Chromebook with an ARMv7 processor, but I doubt you want to go through that much work. Does the Alpha have an Intel processor?

Non stop booting - Help!

Hi,
I downloaded Phoenix OS 64 bit exe. Ran the app, and installed the OS on the same partition "C" on which I have Win 10. As the installation gets done, I restarted the laptop. It asks to boot in to Win 10 or Phoenix OS. I chose Phoenix, but the system rebooted to the same options to choose from Win or Phoenix.
Is there any fix

Hello?

Does grub give any errors after selecting Phoenix? Does any white on black text appear after selecting? Which version do you use and what kind of hardware (CPU/GPU)? Next time give more information from the beginning, maybe you could have gotten more help.

theflippa said:
Does grub give any errors after selecting Phoenix? Does any white on black text appear after selecting? Which version do you use and what kind of hardware (CPU/GPU)? Next time give more information from the beginning, maybe you could have gotten more help.
Click to expand...
Click to collapse
No!
As the Phoenix OS installer finishes the installation, I restarted the Windows. It showed me a screen to select from Win 10 or Phoenix. I chose Phoenix, a white text appear with a black background. Screen kept flashing for 3 to 4 times, without any text. I kept waiting for the Phoenix OS, but it booted me again to the first step to choose from Win or Phoenix.
My BIOS setting is Legacy. I tried to change it to UEFI, it showed me some error that device missing or something.
Laptop Specs:
AMD A8 series APU, 6 GB RAM, 500 GB HDD, Radeon Mobility R5.

BUMP!

I downloaded the ISO file and made a bootable USB with Rufus and it does the same thing just reboots after installation no errors even if I try to boot without installation from the USB it just keeps rebooting I'll try to find a different version tomorrow maybe it'll work

Same, I never got it to work with NTSF...

same thing happened to me.
in my case it shows language selection window and then agreement window, then right after it freezes and computer reboots.

same as me. my laptop is restarting into windows while choosing prime os or phoenix os( i tried both methods with exe file installation or iso for prime os)

the pheonix os i downloaded is the best it boots into the os then the caps lock starts blinking and it reboots back in the selection screen.. i looked online for fixes and everyones saying to turn off the wifi adaptor and use a lan cable. but whats the point of doing this. like honestly remix os does the job but it dosent have the proper keymapper for gaming other then that its great. lets just face it pheonic os is a piece of ****

Hey man, I just faced this issue and can't seem to find any solution so far, so if you've figured a solution for this can you please share it with me ... Thanks.