I have a m150 that has been having issues, a few months ago it randomly started crashing and going into kernel panic.
I've gotten a new phone since then but thought this would be something I could tinker with, and try to get it working again.
However, I seem to be running into problems everywhere.
For starters, It won't let me do a factory reset from the normal settings menu and I cannot boot into recovery mode directly from the phone.
I was finally able to boot into recovery using adb but all it gives me is the picture of the android w the red warning sign and "no command" After that, I tried to reboot into the bootloader using adb.
However, this has only caused the phone to shut down and become unresponsive until removing the battery, or sends it into bootloop. I have the stock rom from lg and want to flash it but I can't unlock the bootloader because even get into it:crying:
sorry if I sound noobish or put this question in the wrong place, I'm new at this.
android ver: 7.0
kernel ver: 3.10.49
developer options are enabled as well as USB debugging and Enable OEM unlock
Related
***
SO I AM RENDERING THIS NEXUS 5 DEAD (BRICKED FOREVER)
***
My daughter was using this Nexus 5 device and the power button started causing her problems.
Well I removed the power button and ordered a new one. So now the power button is not an issue.
But I guess during the time that the phone constantly kept rebooting due to the bad power button, something got corrupt.
Now the device gets to the boot animation and never goes any further.
There are no options in recovery for me to use.
I have working ADB and Fastboot on my PC. I can see the device with Fastboot but not ADB because I can't get the device to boot into the OS for me to enable USB debug.
But I know ADB works because I used it just the other day on a Galaxy S5.
I have tried to run fastboot oem unlock, it unlocks the device then once you reboot the boot loader, it says locked again.
I have tried using Nexus Root Toolkit and hit unlock and it unlocks then says the phone will reset itself and just be patient. It may appear to bootloop but just wait.
I waited for an hour and still just sits at the boot animation.
What are my options without being able to enable USB debug since the device will not boot to the OS?
I am able to Temporarily boot to a custom recovery, but I can't mount data!!!
With Temporary TWRP, I am able to use ADB and I get a success message when I push a new system image to it, and when I push twrp recovery to it, but when the phone reboots, I find out that neither the system image or recovery were actually installed.
I looked into bad partitions, tried some fixes, and nothing works. I am so far beyond frustrated with this thing. I guess I will wait one more day to see if anyone else has any other ideas for me to try, then I am just going to put it in the trash.
- Bootloop
- Bootloader doesn't stay unlocked
- Unable to mount storage
- USB Debugging is not enabled and can't be enabled
- Can't install OS image
- Can't install Recovery
- Can run TWRP temporary
- Can use ADB when TWRP Temporary is running, still can't mount anything
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Whether it can enter REC？
cyclo111 said:
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Click to expand...
Click to collapse
You can try sideloading the full OTA. That doesn't require an unlocked bootloader.