Hello!
I had installed Chupa Chups Rom (Lollipop version) on my D855. I installed the 3minit app which came with it, and I'm stuck in a System UI crash loop. I tried to boot the device into recovery through adb, but I get a message in the command prompt saying the device is unauthorized. Debugging has been enabled on the phone, however. The power button+vol down key command is not triggering the recovery (custom recovery exists), when pressed during boot. Is there any way I could boot into recovery? And will flashing a new firmware using the LG software (kdz firmware flash) wipe my internal memory and app data? Please help me out!!
A million thanks in advance!
Related
Hi,
My 2 year old Micromax Canvas Magnus A117 was working fine till I installed TWRP recovery yesterday. I installed TWRP recovery img file for my phone. The version was twrp-2.8.6.0-a117.img. It downloaded and asked me to verify the location of dev/recovery . I verified it and started the flashing process. At first it took a long ting but said flashing unsuccessful. It asked me to try a second time. I did it and it was successful. TWRP now told me to boot into recovery mode. I pressed the green 'Yes' button but nothing happened. (In the mean time I uninstalled some apps as TWRP ate about 350mb of internal storage during the flashing process.). Then I tried quick boot(reboot) app to boot into recovery. But then the problem started It switched of my phone and then booted but it got stuck at the micromax logo. I pulled out the battery to switch it off, put it in and restarted the phone using the power button. But it got stuck again at the boot micromax logo. I tried booting it in recovery mode (power+volume up) but it flashed off the screen and again booted but not in recovery mode.It got stuck again and agian. The recovery mode seems not to work.
Inthe meantime I connected my phone with adb. adb seems to recognize my device. But when I tried to push flash_image file to my device to flash it with twrp recovery via adb it says "failed to copy d:\flash_image' to /sdcard/flash_image' : Permission denied.
I used this command "adb push d:\flash_image /sdcard/" without quotes. I stored the flash_image file and twrp recovery and stock recovery imgs in the d drive. I also tried fastboot with commands " fastboot flash recovery d:\recovery.img" (I renamed the twrp-2.8.6.0-a117.img to recovery.img). This shows <waiting for any device>and nothing else. Also "adb remount" command says "operation not permitted".
I am at a loss to what to do now.. My recovery.img seems to be not working anymore not the stock neither twrp.
What are my options now? Is my device bricked? I really need a help here.
P.S- I rooted my phone using Framaroot 1.9.3 and it rooted fine installing supersu. And my android version is 4.2.1
Need sometime to get info on this, plz be patient :good:
Alright.
Is there any forum dedicated to my hone in xda?
rijuroy said:
Is there any forum dedicated to my hone in xda?
Click to expand...
Click to collapse
Try posting this post in XDA ASSIST
http://forum.xda-developers.com/general/xda-assist
I am totally stuck: My nexus 9 does not boot anymore (actually it boot but I have a black screen with battery and wifi logo at the right hand corner.
I only can access the boot loader (fast boot mode) and the default android recovery which no allow me to do a lot of things...
I tried to download the Nexus Root Toolkit to try some fix but EOM is locked and adb debugging is not activated in OS (and OS crashes).
Please do you have a solution for me ? Thanks a lot...
Did this happen after an OTA update by any chance?
If so you could try the following: -
If you can get into recovery, you might be able to sideload the OTA again: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
February OTA available from here https://gist.github.com/jduck/3ea03fb3ec1a55544842
Click to expand...
Click to collapse
If it was not from OTA update a factory reset might resolve your problems.
Thank you for the reply
I tried to download an update and transferred it via adb sideload, but I got the error "system partition has unexpected contents".
I also tried to do a factory reset (from HBOOT and from android recovery), but now the system crashes on the setup wizard.
I get "Setup Wizard isn't responding.", and "Unfortunately, System UI has stopped." and I cannot open settings, enable usb debugging and unlock EOM lock.
poussinvert said:
Thank you for the reply
I tried to download an update and transferred it via adb sideload, but I got the error "system partition has unexpected contents".
I also tried to do a factory reset (from HBOOT and from android recovery), but now the system crashes on the setup wizard.
I get "Setup Wizard isn't responding.", and "Unfortunately, System UI has stopped." and I cannot open settings, enable usb debugging and unlock EOM lock.
Click to expand...
Click to collapse
Any chance it is still under warranty? RMA it with Google/HTC (or wherever you bought it).
Yes... this is probably my last chance.. unfortunately
If anyone else has another solution I'm interested
Is it possible to install a new rom with adb sideload from the default recovery ?
Is there a solution to reinstall the original rom without EOM unlocked ?
Hello,
I'm stuck into a similar situation reported here [Q] Volume down not working, how to get into recovery? on my LG G5 H850.
I had MM installed and finally wanted to upgrade to N having heared the good news concerning Xposed's availability.
So I've patched the bootloader and then a 20k Complete Stock ROM through TWRP still installed and fully working at this moment.
Boot back to N. OK
Once the upgrade process have finished I had the surprise to discover that I have all my previous apps and settings where still present but I have dozens of FCs polluting the screen !!
e.g. I cannot access com.android.settings
The phone is almost unusable :crying:
Before the upgrade I made some wipes (cache, system I guess and if I look back into my memory) but I don't remember having made a factory reset ... my bad
I don't have root anymore :good:
I made
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.1.x.x.x.img
but cannot "stick" it coz of my volDown button HS
Code:
adb reboot recovery
finishes to a "No command" screen (maybe because of an un"stick"ed twrp)
Code:
adb reboot bootloader
fastboot boot twrp-3.1.x.x.x.img
but got a "FAILED (remote: unknown command)" response
I still have the Official TWRP app manager installer but cannot install a new one (because of the "su" lack)
Questions :
Is there a way to reinstall "su" binaries in these conditions and without TWRP ?
Is there a way to "live" boot into a recovery ?
What can I do with "fastboot boot <something>" ?
Pleease someone ... one good news :fingers-crossed:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
DOWNLOAD
TWRP 3.2.3.0
Flashing Instructions
Make sure you have fastboot drivers installed and your bootloader is unlocked
Download the file
In fastboot open the directory of downloaded file and type
fastboot flash recovery recovery.img, after that type
fastboot oem reboot-recovery, You'll have a black screen on your display wait for 5-10s you'll be greeted with TWRP screen if you still didn't get the screen then press power button 2-3 times
BUGS
Data decryption ( For this you need to select Wipe -> format data (You'll lose all your data in this process) )
No Battery% ( I purposefully disabled it as the battery% always stays at 50% so I'll find the battery% path and fix this in the next build)
Flash force encrypt disabler in recovery to fix magisk module installation and other data partition related issues.
Source Code: TWRP source, Device Tree and Kernel Source
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
pankajyadav_18 said:
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
Click to expand...
Click to collapse
By reboot problem if you mean, the phone getting restarted randomly in loop then the only way to fix it is to go to the service center.
I flashed TWRP to the device successfully, and proceeded to try to install Magisk 19.3 zip. It would begin to do a recovery bootloop. I fixed it using TWRP, and tried using the patched boot img from magisk manager instead. This is where things go wrong. After flashing boot.img, the phone refuses to boot, and asks me to do a factory reset. I did this twice, and the phone continued not to boot. I then tried installing the latest android Q factory image. The flash failed, and the phone stopped showing up when I do fastboot devices or adb devices. It is stuck in the bootloader telling me slot b is not bootable. I have tried different ports, but adb and fastboot are no longer responding.
Take out the battery for 10 sec or more replace, see if you can get back into recovery. Recovery should be TWRP.
You may need to uninstall and reinstall the driver on your computer. IF it is a Win computer should show up in device manager at the top under Android.
https://www.xda-developers.com/how-to-install-custom-rom-android/
or you can do a factory reset which is also a button.
I fixed it by holding down the power and vol up buttons, which allowed me to use fastboot again and fixed everything. Thanks for the help tho>