Related
Ok, here's what's happening. I go to flash a ROM, Kernel, whatever, and 8 times out of ten it just doesn't work correctly. I make my way to the "data reset" and click it, then the screen goes blank. I can hit power and it brings me back to where I was, but it won't let me run it. Same goes for choosing a zip file, or even when trying to reboot phone from CWM. It's not really any command in particular. Sometimes when I click, it goes to the green guy with the spinning thing in his chest, and just hangs there. I have to do a battery pull, go to bootloader, then recovery, and then it will work again, whatever command I was originally trying. ALSO, the up and down cursor, aka the volume button, is SUPER sensitive. I can click it once, and it'll go down or up 3 to 5 spaces. This I can deal with, but having to pull the battery to reset it again just sucks. Any ideas or help? I did "report error" and sent an email, but got nothing.
On the second part it is not intercepting the power command so instead of detecting that you are trying to select an option on the boot menu instead shutting the screen off. I had this problem on my nexus one but I was able to get by it with the trackball. Try installing rom manager from the market and reflashing clockworkmod.
Sometimes when you are using the volume keys to go up and down the menu and it does that fun little "skip 5 items" mess, you will get a message that says "system menu disabled" or something weird along those lines. That will prevent you from using the power key to hit "enter". To fix it just hit the up and down volume keys like crazy until you see "system menu enabled" or whatnot.
Also, if you go and flash the touch enabled cwmr from the apps (I think) board here, it pretty much fixes that.
Hope that helps you out.
lonnyrs said:
Ok, here's what's happening. I go to flash a ROM, Kernel, whatever, and 8 times out of ten it just doesn't work correctly. I make my way to the "data reset" and click it, then the screen goes blank. I can hit power and it brings me back to where I was, but it won't let me run it. Same goes for choosing a zip file, or even when trying to reboot phone from CWM. It's not really any command in particular. Sometimes when I click, it goes to the green guy with the spinning thing in his chest, and just hangs there. I have to do a battery pull, go to bootloader, then recovery, and then it will work again, whatever command I was originally trying. ALSO, the up and down cursor, aka the volume button, is SUPER sensitive. I can click it once, and it'll go down or up 3 to 5 spaces. This I can deal with, but having to pull the battery to reset it again just sucks. Any ideas or help? I did "report error" and sent an email, but got nothing.
Click to expand...
Click to collapse
Recommend you remove the file /system/recovery-from-boot.p with root explorer and reflash the touch screen one. The multi click with the volume is a known problem and the touch will fix that. Also, recovery-from-boot.p will wipe your clockwork every time u restart, making it troublesome to flash unless u want to reflash CWM with rom manager every time u want to flash something. Just take it out and put it in whatever folder u keep everything u change on ur phone
Its exactly as coverton341 says. CWM is disabling your Power Button as an enter button because of a bug. I don't even think you have to hit the volume buttons like crazy to get it back....it seems to timeout and come back on its own after a minute.
KernelK said:
Its exactly as coverton341 says. CWM is disabling your Power Button as an enter button because of a bug. I don't even think you have to hit the volume buttons like crazy to get it back....it seems to timeout and come back on its own after a minute.
Click to expand...
Click to collapse
yea i actually do remember that when i was running the non touch screen. I did just let it sit and it'll time out. Touch screen has a flashable zip tho so its super easy to just bypass this
Weell it looks like they do help people out, although it took the a month bbut hey i already have a replacement ouya from gamestop, making this information something useful for future references, maybe this helps with other things too, this weas sent by the developer team at ouya
Piers (OUYA Support)
Hi,
I hope this finds you well. In the interest of time it sounds like your OUYA may be bricked, but there's a fairly good chance you can recovery your OUYA. Please follow the steps below and let me know if this has restored your OUYA. Thanks, and sorry about our delay in responding!
Best regards,
Piers Sutton
Developer Support
1) Plug a USB keyboard into your OUYA while it's powered off.
2) Power on your OUYA and let it boot as far as it can.
2.5) Find the sysreq key on your keyboard. On most extended keyboards, it is Print Screen.
3) Hold down Alt and Print Screen
4) Press and hold ALT and Print Screen (sysreq) Key.
5) Press i and hold for 5 seconds then release. Repeat this step for 30-45 seconds.
6) Press the HOME key
7) Select "wipe data/factory reset" and hit Enter key.
8) Select "Yes -- delete all user data" and hit Enter key.
9) Select "wipe cache partition" and hit Enter key.
10) Select "reboot system now" and hit Enter key.
treborbula1 said:
1) Plug a USB keyboard into your OUYA while it's powered off.
2) Power on your OUYA and let it boot as far as it can.
2.5) Find the sysreq key on your keyboard. On most extended keyboards, it is Print Screen.
3) Hold down Alt and Print Screen
4) Press and hold ALT and Print Screen (sysreq) Key.
5) Press i and hold for 5 seconds then release. Repeat this step for 30-45 seconds.
6) Press the HOME key
7) Select "wipe data/factory reset" and hit Enter key.
8) Select "Yes -- delete all user data" and hit Enter key.
9) Select "wipe cache partition" and hit Enter key.
10) Select "reboot system now" and hit Enter key.
Click to expand...
Click to collapse
sorry you didn't find this forums earlier. we could have probably helped you out without getting a replacement console.
thanks for the write up though. this same info is already on here (a bunch of different places) but having it again never hurts.
now that you have a working console, look into CWM. its a replacement Recovery Mode that gives you a lot more options and is easier to access. from recovery, you can also re-flash a stock update and that will help A LOT in brick situations.
just ask around for help. and use the search function. not necessarily in that order :silly:
treborbula1 said:
Weell it looks like they do help people out, although it took the a month bbut hey i already have a replacement ouya from gamestop, making this information something useful for future references, maybe this helps with other things too, this weas sent by the developer team at ouya
Piers (OUYA Support)
Hi,
I hope this finds you well. In the interest of time it sounds like your OUYA may be bricked, but there's a fairly good chance you can recovery your OUYA. Please follow the steps below and let me know if this has restored your OUYA. Thanks, and sorry about our delay in responding!
Best regards,
Piers Sutton
Developer Support
1) Plug a USB keyboard into your OUYA while it's powered off.
2) Power on your OUYA and let it boot as far as it can.
2.5) Find the sysreq key on your keyboard. On most extended keyboards, it is Print Screen.
3) Hold down Alt and Print Screen
4) Press and hold ALT and Print Screen (sysreq) Key.
5) Press i and hold for 5 seconds then release. Repeat this step for 30-45 seconds.
6) Press the HOME key
7) Select "wipe data/factory reset" and hit Enter key.
8) Select "Yes -- delete all user data" and hit Enter key.
9) Select "wipe cache partition" and hit Enter key.
10) Select "reboot system now" and hit Enter key.
Click to expand...
Click to collapse
Wow I never knew you could do this! Thanks for writing this up, it might be very useful someday
This is known. But if OUYA is sending this out as their tech support, you'd think they would see the benefit in giving us an easy way into recovery, instead of making us think we are an insignificant minority.
I'm glad you got a replacement, but I am still dissappointed in OUYA reguarding this issue.
Sent from my HTC One using xda premium
adb sideload
I've tired to wipe cache and user data. But my OUYA still can't boot.
Then I tried, to sideload:
adb sideload RC-OUYA-1.0.328-r1_ota.zip
but I got the following error message:
assert failed: !less_than_int(1368745818, getprop("ro.build.date.utc")
Installation aborted.
How can I sideload an ouya ROM?
im not sure you can sideload a ouya rom, you need root and a recovery to flash a rom, just in case and pardon my ignorance but i havent looked into it much, but try searching the ouya forum, that'll help
You cant flash an ota over a broken or custom rom since ota dont contain the full os but just the changes for the update. We would need a propper backup or system dump etc to flash from recovery or an IMG to flash via fastboot.
Gesendet von meinem One X+ mit Tapatalk 4
treborbula1 said:
1) Plug a USB keyboard into your OUYA while it's powered off.
2) Power on your OUYA and let it boot as far as it can.
2.5) Find the sysreq key on your keyboard. On most extended keyboards, it is Print Screen.
3) Hold down Alt and Print Screen
4) Press and hold ALT and Print Screen (sysreq) Key.
5) Press i and hold for 5 seconds then release. Repeat this step for 30-45 seconds.
6) Press the HOME key
7) Select "wipe data/factory reset" and hit Enter key.
8) Select "Yes -- delete all user data" and hit Enter key.
9) Select "wipe cache partition" and hit Enter key.
10) Select "reboot system now" and hit Enter key.
Click to expand...
Click to collapse
Why are steps 3 and 4 the same?
Please, double-check your post for clarity. How long are we supposed to hold down ALT+PrintScr, how many times are we supposed to press them?
I believe it is a case of bashing away on the key as much as possible to hopefully hit it at the right time. Very hit and miss
Sent from my Nexus 5 using xda app-developers app
My understanding is this is the process for a 'hard reset' correct? A complete reinstall of the OS wiping back to factory (not a factory reset).
I ask because I have xposed and the mod collect and would like to completely wipe any modification and start fresh.
Additionally, you do not need to adb the OS in correct? Other instructions stated you needed to side load an ota (a newer version at that) and I would prefer not to have to adb in.
Last question. My TV shows no input when you hit the 'home' key following the above steps. I'm assuming its just defaulting to a resolution my TV cannot display, not a problem with the bootloader?
Stock ROM BTW.
robinscp said:
I believe it is a case of bashing away on the key as much as possible to hopefully hit it at the right time. Very hit and miss
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Don't know if this will help anyone.
In my case it was going into update mode, rebooting and then getting the red exclamation mark, it would reboot, try to do the update and go back to the exclamation mark again, just cycling through, and through, and through and...
I couldn't get ALT-PrintScreen to work, and it was p*ssing me off royally. Then during the loading update part I pressed the ESC key basically in frustration, which cancelled update and took me back to the menu and I did the factory reset through the System menu option. I now have a working Ouya.
After a few hours of struggling with the ALT-PrintScreen option I was surprised by my accidental result.
tazeo said:
Don't know if this will help anyone.
In my case it was going into update mode, rebooting and then getting the red exclamation mark, it would reboot, try to do the update and go back to the exclamation mark again, just cycling through, and through, and through and...
I couldn't get ALT-PrintScreen to work, and it was p*ssing me off royally. Then during the loading update part I pressed the ESC key basically in frustration, which cancelled update and took me back to the menu and I did the factory reset through the System menu option. I now have a working Ouya.
After a few hours of struggling with the ALT-PrintScreen option I was surprised by my accidental result.
Click to expand...
Click to collapse
Used your accidental method and works like a charm
I really bricked this thing and need help
I totally borked my ouya and think it's bricked...
I flashed safe recovery and then flashed CWM from within that and got stuck in the boot loop.
I then side loaded a rom which changed nothing. In an attempt to get out of the cwm--safe recovery loop, I flashed the bootloader (with apparently no kernel) and now have persistent black screen.
I am unable to get anything working via alt-prt scrn-i combo even using home button and device no longer shows up in ADB or in windows.
Am wondering if anyone has any last ideas?
Thanks,
Josh
Jc_Dent0n said:
I've tired to wipe cache and user data. But my OUYA still can't boot.
Then I tried, to sideload:
adb sideload RC-OUYA-1.0.328-r1_ota.zip
but I got the following error message:
assert failed: !less_than_int(1368745818, getprop("ro.build.date.utc")
Installation aborted.
How can I sideload an ouya ROM?
Click to expand...
Click to collapse
You can only sideload a rom which is the same version currently installed or newer, trying to sideload an older rom will give this error message.
took me ages to work this out.
Need help here guys.
I reinstalled CWM and wiped dalvik/cache
Now I cant even boot to recovery no matter how I tried.
I can access the OUYA through the micro usb and can read the file structure from my Mac
How do I restore?
Brickt my ouya trying to flash a recovery.
Flashed it using fastboot. Since then it always boots into CWM, I can see the CWM logo, but thats all thats on the screen. ADB sees my ouya, sometimes, but trying to do anything gives me a protocol fault (no status)
Now Im trying to use this to just reset everything but at about the 4th or 5th time pressing i with alt and sysreq my ouya powers down...
Anyone have any advice?
moku160 said:
Brickt my ouya trying to flash a recovery.
Flashed it using fastboot. Since then it always boots into CWM, I can see the CWM logo, but thats all thats on the screen. ADB sees my ouya, sometimes, but trying to do anything gives me a protocol fault (no status)
Now Im trying to use this to just reset everything but at about the 4th or 5th time pressing i with alt and sysreq my ouya powers down...
Anyone have any advice?
Click to expand...
Click to collapse
Same thing happens to me when I try the recovery. What is the last thing you see when hitting the key combinations? U Splash screen?
substance.v said:
Same thing happens to me when I try the recovery. What is the last thing you see when hitting the key combinations? U Splash screen?
Click to expand...
Click to collapse
The last thing I see, the only thing I see ever, Is the background with the gear and hat for CWM recovery. No menu just the background. After pressing the buttons down for 4 or 5 times it powers down. That's it
moku160 said:
The last thing I see, the only thing I see ever, Is the background with the gear and hat for CWM recovery. No menu just the background. After pressing the buttons down for 4 or 5 times it powers down. That's it
Click to expand...
Click to collapse
Is it possible to post a screen shot with your phone. also connect it to your computer via usb and show us a screen shot of your device manager?
Make sure you have the drivers installed.
Regards-
moku160 said:
The last thing I see, the only thing I see ever, Is the background with the gear and hat for CWM recovery. No menu just the background. After pressing the buttons down for 4 or 5 times it powers down. That's it
Click to expand...
Click to collapse
I got fixed... so lets try this.. power one OUYA with keyboard attached. As soon as the LED lights up on the unit... press alt+sysrq+i .. keeping alt and sysrq pressed .. tap the I until your screen blinks twice. this should bring you into the recovery mode. If your ouya is connected to a computer, you will here a chime.. you device manager should show this as Android Composite ADB interface. from here you can push your image and flash ROMS and such.. hopes this helps
hi everyone, i received today my phone, it seems to be a korean import unlocked for sims but not rooted.
i had a galsaxy s2 for a few years and know how to root and flash a rom, but problem is, on my htc one m8 there is no option to disable fast boot in the battery menu
i looked everywhere on the phone, it's just not there. i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore, links are dead, any suggestion?
thanks
anybody can help with this? I'm bloody stuck without a rooted phone!!!! thank you
satello said:
i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore
Click to expand...
Click to collapse
Is your main problem not being able to get into bootloader (I don't see how else the fast boot power option would prevent you from rooting)? Just hold the power button until the options come up, select Restart, then when the screen goes black, immediately (before the white HTC boot screen) hold the power down rocker, and don't let go until hboot appears.
Alternately, hold power and vol up to force a reboot of the phone, then when the screen goes dark, switch to holding the vol down rocker.
Why are you worry so much on "fast boot" ?
You don't necessarily need to press power + volume down to go to hboot/bootloader.
I never disable "fast boot". Just simply restart, wait for the downanimation complete (it turn black screen) then press volume down (no holding power button) ... it will go to hboot.
Or you can plug in your device to PC with USB debugging enabled. Open a command prompt from your adb folder, type command adb reboot bootloader
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
I bet you do have a clone, does the phone has a playstore ? Install some phone specs app and see what it comes up with.
satello said:
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
Question is... Have I got a clone here??
Click to expand...
Click to collapse
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
ckpv5 said:
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
Click to expand...
Click to collapse
it looks like that, checking the specs i can see a ARM v7 Processor, rev3 and a screen resolution of 1280 x 720...
Unfortunately, I think your device is a "Clone".
thanks guys, i've haven't been rooting for a couple of years, but really thougt something was wrong, terribly wrong. ok, will check back here when i get a real one, if needed.
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here. Nevermind. And yes, that phone is/was a clone
CNK80Q3MX said:
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here.
Click to expand...
Click to collapse
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
redpoint73 said:
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
Click to expand...
Click to collapse
Thanks. I was looking for an explanation like that; in fact, somehow that's why I ended up in this thread. Though, it's useful yet, since there must be lots of devices still running the 'Fast boot' option due to certain manufacturer's lack of firmware updates and because not every device in need for support out there is actually a new device
Sent from my LG-D693n using XDA Free mobile app
same problem
satello said:
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
Click to expand...
Click to collapse
oh man, i thought i was the only one !
i have the same exact phone !
my serial number is exactly 123456789ABCDEF !!!
mine is a chinese mtk htc one m8. after hours of search i figured my phone name is alps_htc one m8 and yes my friend, is a fu..... clone !!!
i tried everything ! and search whole bunch of websites and forums like xda and xda itself, nothing happened !
i also get the => fastboot....... every time i try to go to bootloader !
this is something that you guys who trying to help here had to understand, these clone phones settings is completely different from other phones and even the original one ! hold power button then hold volume up or down, doesn't work !
every time it stock in => fastboot..... none of the buttons of the damn phone works and i have to wait until the battery drain ! real pain in the ass !!! because you know, htc one m8 does not have battery removing option, another pain in the ass !!!!!!!!!
i had a another problem too, when i wipe this clone phone, amazingly, the IMEI was gone !!! the phone said "invalid IMEI" !!! witch after hours of search i flashed it with an app from mobileuncle tools, thank to them amazing app allowed me to flash a custom IMEI from a unused phone.
now i use another htc device from the original manufacturer.
a little piece of advice, do not buy a clone phone ! cause it's going to piss you off !!!
and if you don't know how to recognize a clone from a original phone, its simple, just check the serial number, if it's feel weird, just give back the phone to seller, smile, and run out of the store !
thanks to XDA btw.
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
Please ensure you REALLY use the correct key combo! Just saying bla does not tell us what exactly you tried.
If you really can't get in you can try to Boot into download mode
https://m.youtube.com/watch?v=0cbLhpWq5C8
Then use lgup to reinstall stock ROM and do all the stuff again to get twrp, root and a custom ROM.
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
raptorddd said:
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
Click to expand...
Click to collapse
Thank for your answer ! No it couldn't even boot in download mode
I resolved my problem by forcing again the buttons to reset completely, it finally showed me after about 30 boots or more the reset screen, I said "ok" ; and in fact it just rebooted saying "updating Android", I did not lost anything.
I still don't understand how it happened but anyway !
I don't know if it's possible to set the topic as resolved ? I don't find it
Hello.
When I reboot the device using the classic switches and choose reboot, reboot the device twice.
The Poco logo will start, then the miui animation, at this point the device will restart again.
Then it will boot into the system normally.
However, if I use third-party switches, for example, restart the device only once, as it should be.
Or if an application, such as magisk, needs a restart - reboot, then also restart the device only once as it should be.
Don't know what it can be? In my opinion, the classic stock power menu will be to blame.
Hmm maybe something to do with modifications, unless it causes any problem im sure it'll be fine