I'm a bit stuck here, would appreciate some assistance.
I tried to root my device (UMI Plus) by yesterday using 'SP Flash tool' by flashing TWRP and then installing SuperSU. That went fine, but after booting my Google Play Services kept rebooting rendering the device unusable. In an attempt to fix this I tried a "Factory Reset" via the Android settings menu which I guess was a bad idea because it started auto booting into Recovery... At that point no matter what I did I ended up back in Recovery.. Reboot to system, factory data reset.. all rebooted the phone back into TWRP recovery.
So I thought I would just try putting the default recovery back on the device again but whenever I power off the device and connect it to my PC it boots into recovery.. The phone needs to be powered off for SP Flash Tools to work. Tried loading recovery image via fastboot but the volume rockers don't work in fastboot so I can't confirm the action.
After some digging I read online that holding down VolUp + Power can 'force' into preload mode, which seems to have some success. I can see the device boot into "Preloader mode" in device manager in Windows, but it loses connection after about 3 seconds. So I did that with my SP flash tool ready and it seems to have erased recovery mode. Oops! Now whenever I try to get into recovery it just says "No command". No combination of button pressing, button holding, button releasing or anything will change this (This is the only answer I could find on Google!). Neither fastboot or adb can see the device either. It shows up as "MTP USB device" in device manager in Windows...
Is it doomed? I can't figure out what to do next...
P.S. The full ROM is available here but in RAR format.. which seems strange to me...
http://community.umidigi.com/thread-11462-1-1.html
Poke
I was trying to root my p20 lite on EMUI 9.1 so I flashed the patched recovery ramdisk, rebooted then typed "adb reboot recovery", but it wouldn't load. So I forcereseted the phone but it came to the same screen "your device has been unlocked" and "Your device is booting now" no options to press power to boot or erecovery. So I tried flashing the original ramdisk but it would still never load, and trying "fastboot reboot bootloader" didn't help either. I can't boot into system I can only go into fastboot mode.
edit: adb detects my device but rebooting into system command still reboots into recovery
edit 2: my phone has bootloader unlocked
edit 3: here is the phone log https://drive.google.com/file/d/19MNYSdI5gkzlAti2wVhsGuc8v6iAWaG6/view?usp=sharing
Connect phone to charger
Press and hold power button only
Keep it pressed till phone boots into 3 option scream, 1 press vol up 3 sec for e recovery, 2 press power to enter system, 3 do nothing 5 sec
Release power button, wait
Shoulda enter e recovery
Press reboot and wait
Shoulda reboot to system, root will not work, but phone will work
If want to start with root, you need to relfash system using dload package or hisuite update, otherwise your phone still will be stucked , so need fresh system files
I don’t get the three options. Only the your device is booting now. Rebooting via adb just reboots into the same thing.
edit: let the battery drain and now it is working again
Same, loading screen but nothing.
I tried to enter download mode through recovery mode since I couldn't find the proper key combination for the M31 online. But now it's stuck in a black screen with nothing but the words 'entering fastboot' on top. I can't restart it.
I've enabled developer options and OEM unlock but that's all I did.
Press the power button for a long time (A minute at most)
Thank you!
zequihumano said:
Press the power button for a long time (A minute at most)
Click to expand...
Click to collapse
yo it isnt working pls help me out
Just documenting my (M315FXXU2ATJ9) solution (found through trial and error) in case this happens to somebody.
This is what worked for me:
1. Connect your phone to your PC via USB
2. Hold down VOL_UP + VOL_DN + POWER for 10 seconds
Your M31 will turn off and the charging logo will appear.
You can now simply disconnect the USB cable and turn it on normally.
Hope this helps.
Hello,
I had updated my M315F to official OneUI4.1, but I am having battery issues and the phone is bit laggy, so I decided to revert to OneUI3.1 using Odin tool, however on entering the recovery mode and getting into "Reboot to bootloader", device stucks at "Entering fastboot....", and its unresponsive as download mode doesn't start. The first time I did without unlocking the OEM, but even after unlocking the OEM and entering the bootloader, it says "Entering fastboot...., so again restarting phone and repeating the same process. Download mode doesn't start.
Is there anyway to reboot to download mode?
Thanks in advance
Help is much appreciated
Regards
Long story short, I messed up and I regret it. I edited the SDK 2 API levels up to get an app to possibly work and didn't think of the consequences of everything else.
I was running 8.0.0 rooted and am unable to get into recovery as the main boot of android is messed up where all apps result in continuous errors and when trying to enable usb debugging in the settings, the settings crash.
If I could get into revovery mode, I can fix it. The issue though is holding power + vol down does not work. I am not sure how to get into the recovery when the v30 shows that conformity screen on boot when the boot loader is unlocked. I was able to get into fastboot mode but on that screen it says i need to enable OEM unlock. Sadly that is not working as settings crash when trying to enable.
Would anyone have any other ideas to get to recovery?
Let me know if any more info is needed.
EDIT: I do have LGUP installed and does see the device. I would prefer not to have to fully reset the device if possible. Can LGUP boot the device into recovery?
What you described (just holding power and volume) will not get you into recovery... the proper sequence (aka the "button dance") is more involved than that. If you're only holding down those buttons, then you're not doing the process... do a search to see what it is (I believe you need to release and then re-press the power button... but I don't recall, so certainly don't take my description as enough info.
You also said you can boot into fastboot - you may be able to "fastboot reboot recovery" to get into recovery... some phones respond to that.
raycekar said:
If I could get into revovery mode, I can fix it. The issue though is holding power + vol down does not work. I am not sure how to get into the recovery when the v30 shows that conformity screen on boot when the boot loader is unlocked. I was able to get into fastboot mode but on that screen it says i need to enable OEM unlock. Sadly that is not working as settings crash when trying to enable.
Would anyone have any other ideas to get to recovery?
Let me know if any more info is needed.
EDIT: I do have LGUP installed and does see the device. I would prefer not to have to fully reset the device if possible. Can LGUP boot the device into recovery?
Click to expand...
Click to collapse
LGUP can get you to Download mode but not Recovery.
You can boot to Recovery (TWRP) with hardware button dance.
8 sec Power + Vol-, and when it shuts off, release both, immediatly press both again (at the same time), and as soon as the LG V30 logo appears, release power and press/hold it again.
Should get you to the factory reset menu, confirm twice with "yes" (navigate via vol/power buttons), and TWRP should boot fine.
Might take a few tries to get the right timing for that
Click to expand...
Click to collapse
For that, remember the annoying bootloader unlock warning is part of the boot sequence, if you still have that.
ChazzMatt said:
LGUP can get you to Download mode but not Recovery.
You can boot to Recovery (TWRP) with hardware button dance.
For that, remember the annoying bootloader unlock warning is part of the boot sequence, if you still have that.
Click to expand...
Click to collapse
@schwinn8 -
I ended up doing a clean flash with LGUP as I need my phone for work and thought this might as well be a good time to update from stock oreo to stock pie. I wish I had remembered the master reset method as that should have throw me into recovery, I was releasing and then holding both power and vol down when it should have just been releasing power and then holding while continuously holding vol down. Along with fastboot, a while back I had to reinstall windows and so not thinking things through, I did not have working fastboot drivers and didn't initially realize it.
Mistakes were made :/
I very much appreciate the reply.
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
My M4 (E2312) have pretty much the same symptoms: can not boot anything and just stuck on SONY logo, Flashtool does not recognize phone in flashmode (Vol -), just fastboot. And using fastboot to flash system, boot, recovery shows finished processes but phone does nothing new. And phone does not response well to USB, only after a reset then it updates the status.
I have Pexo ROM v3, custom TWRP, SkyMelon 9 I think,Rooted SuperSU and Magisk( has conflicts so when I boot some pop up says X app has stopped working. When I install some more apps to use it was ok, then the pop ups show up more and more and then it decides to boot loop to the stage we are now.
I have tried install 0.9.33 and 0.9.23.1( somehow only 0.9.23.1 can install 3 drivers), Xperia Companion, Emma, ggsetup 3.2.0.1, Driver SONY so0104 (so0113 ADB interface- status show it cannot start),
So either it is the drivers on computer, the computer USB ports, the phone's software or hardware defects lead to software that caused it.
bdnlspam said:
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
Click to expand...
Click to collapse
Yes, I also tried installing conceptify but it doesnt work. At this point its better if you stick with the stock rom, remove as much bloatware as possible and consider it a phone because almost none of the ROMs here work stability wise, or they maybe stable but some features like display brightness or speakers dont work. So I recommend you install stock rom via flashtool and then unlock the bootloader via flashtool again and install twrp again. Also if possible try reinstalling the drivers for the phone in flashtool. Hope this works mate.
Not my name said:
Also if possible try reinstalling the drivers for the phone in flashtool.
Click to expand...
Click to collapse
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
bdnlspam said:
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
Click to expand...
Click to collapse
Can you try it on a Linux PC I guess?