i have an old ale-l21 italian phone (i don't remember if its single or dual), a long time ago after downgrading from nougat to marshhmallow with rollback update etc i lost my imei i tried everything to fix this, followed thousend of tutorials flahsing a lot of firmwares, official and not, after a lot of tries a new issue comes into play, after like 30 seconds from boot the phone shutdown automatically and reboot itself. the issue is not the power button because in fastboot mode its staying there aswell as twrp recoveries, in the stock recovery also reboot itself after 30 seconds while trying to force update with dload, now dload fail everytime even before the reboot issue. the phone can still charge but after a bit the phone boot automatically, random time. the only stable state to charge are fastboot and twrp. the bootloader is obsviously unlocked. in the windows of 30 seconds i managed to setup the phone (reboot issue) unlock develeper in options (reboot issue) enable debug usb (reboot issue) trust the computer for debug, then i captured the last lines of an adb logcat. someone can help??
Related
Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)
Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image
Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.
Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...
Go to a friend with Windows.
Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!
How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.
My 2012 N7 is stuck in a boot loop. It is stock 4.4.4 and not rooted or bootloader unlocked.
Sometimes it will hang during the boot animation and start over, if it makes it through a complete boot I get about 10 seconds before it reboots again, sometimes a random app will crash before that (usually TV) but not always. That means I can't make any system changes (turn off MTP, usb debugging), or if I can do it quickly the changes don't persist or there isn't time for my PC to update the drivers.
I have tried restoring through the recovery mode multiple times, that didn't take.
I've tried using WugFresh's NRT v1.9.3 to use its "Flash Stock and Unroot" feature and after downloading Google drivers so it can talk to it during fastboot mode I was able to get it to attempt to flash both the 4.4.4 factory image and 5.0 factory image. None of those worked either, I think maybe because I can't get the USB debugging working. The process goes very quickly and spits back various FAILED (remote: Bootloader is locked.) and nothing happens, just sticks at the bootloader screen. Even tried to unlock the bootloader via the NRT in case that would work, got as far as the option to unlock the bootloader and erase everything, that didn't take either.
Every thing I've tried so far just keeps giving me constant reboots with all my apps and data still there. The Android laying there with his chest open is mocking me now and I'm stuck on what to do next. I need help or a point in the right direction, please I am running at my wits end with the blasted thing.
So I wanted to root my phone (P9 Lite with Nougat). It was my first time so I found a step by step tutorial and used it to progress. After a load of time I finally was able to unlock it, then apparently, I was supposed to install TWRP. Failed a few times then I understood that TWRP version was for marshmallow, so I searched for a version compatible with nougat. Found one, installed correctly, file was transferred. Anyways when I tried to boot TWRP it would not work, it would boot in normal mode. I tried 2 more versions TWRP and it was the same. All that Power button + one of volume buttons **** was not working. So I thought, maybe I just overdone it, with many different versions of TWRP. So I decided to factory reset it. I rebooted my phone, now it is stuck at 'Your device is booting now' and I am frustrated as f**k. Not mentioning problems with unlocking, this whole process was really annoying, been doing this **** for 4 hours straight. Would like to receive some help if anyone got some. Let me know if there is something more you need to know.
Thanks in advance.
EDIT: Tried reinstalling img failes and relocking bootloader using https://forum.xda-developers.com/hu...i-p9-lite-stuck-device-booting-t3539696/page4
Now the phone is stuck at ERROR MODE, Attention! Please update system again
Error!
Func NO: 11 (recovery image)
Func NO: 2 (load failed!)
Bump.
I honestly need help guys. I let battery die, then I use Minimal ADB and FastBoot + (volume down + connecting to pc via usb), phone would start and load system normally to the point where it requires PIN lock. Then it notifies battery is too low and shuts down. After charging 2-4 mins phone starts itself again, with same error screen.
Hi guys!
I've read tons of threads and guides on Google but nothing helped me to bring to life my Samsung Galaxy S8 Plus. After hours and hours of test and probes I surrender!
Basically I was using normally my phone and suddenly has power off and showing the Samsung Galaxy Logo continuously. I've force reboot it with vol down+pwr button and after some minutes restart normally again. After 5min again the boot loop and stuck there. Tried again to power it off but didn't work so I thought was the battery (because is 3yrs old with heavy use and months ago I had the screen flickering and a battery drain to zero). I opened the phone, unplug the battery and the power button (because I thought was the power button stucked as on my father phone). So after mounted all the stuff in their place I tried to boot it and suddenly start to work again! I've backup all my things rapidly but again power off by himself and this is the last time I see it working.
So I tried to empty the cache entering in the recovery but it was useless so the only way seems flashing the original FW with Odin. Downloaded the right one with Frija, upload the rights files in Odin (Home_csc because I don't want to lose my internal memory stuff) and the phone automatically reboots, pass the Samsung logo and go in Upgrading mode with the blue android screen and a % increasing. After that by himself power off and nothing happen.
I read some stuff about my possibilities to recover it without losing data but a lot of tutorial talk about entering in recovery but I cannot do it! Simply does not go in recovery with vol_up+bixby+pwr_button even after force shutdown it with vol_down+pwr_button or reattach the battery. The only thing I'm allowed to do is put it in Download Mode to be recognized by Odin.
I've tried to launch ADB devices but it is not visible in Download Mode.
I've tried to flash another firmware for the same model (theoretically my one is unbranded italian) but I tried with WIND one because in download mode there is a text "Carried_ID:WIND" but this FW Odin fail to upload it.
I've tried to flash the TWRP with Odin but fails on the phone with error "Custom binary(recovery) blocked by FRP Lock". I've searched how to unlock it but without have access to recovery or phone settings seems impossible. And this phone has also OEM Lock.
I've tried again to flash the FW but the only difference than before was the blue android robot with stucked text "Installing system update", "Erasing" , "yellow advice notice" and finally a green screen with "An error has occurred while updating the device software.Use the Emergency recovery function in the Smart Switch PC Software". And yes, I already tried with Smart Switch but the program does not detect the phone.
I've also tried to flash the original recovery but nothing change.
Seems that my devices is bricked or a kind of boot loop.
In my situation there is something that I can do to recover the internal memory data? I don't tried to flash the FW with CSC file because I don't want to erase all the data.
My Galaxy was original since the purchasing, no root or flashed a FW, only OTA updates.
I've attached a photo with the stuff that appear in Download mode.
downloaded magisk, created the patched boot.img
fastboot unlocked
flashed patched boot img
fastboot reboot
device powered on, charging indicator light comes on.
vibratr motor spins for about 10 seconds, screen stays off, restarts and goes again.
tried pressing v+ and power, nothing. all other combos, v-/power, vol+/- and power, nothing.
anyone have any clue how to recover from this?
It also happened with me 2 weeks earlier, but with my tab 4 10, I think its beacause of dm verity (verified boot).
Hopefully you are lucky , but I was not at that time, no one helped me ?, I spent 1 week to come out from that but you can recover your tab with in few minutes.
Just go in your browser and type lmsa.
You will found a lenovo motorola smart assistant website there, just click on it and install that app.
Then open that app , click on rescue and feed your device credentials, it will automatically start downloading the firmware and after downloading, it will guide you to how to connect your device to pc correctly for flashing and then it will automatically restore your device to it's orignal state.
No hassle of installing drivers etc.
And you will have your device working again ?.
First boot will take upto 5 min so be patient.
evilsway said:
downloaded magisk, created the patched boot.img
fastboot unlocked
flashed patched boot img
fastboot reboot
device powered on, charging indicator light comes on.
vibratr motor spins for about 10 seconds, screen stays off, restarts and goes again.
tried pressing v+ and power, nothing. all other combos, v-/power, vol+/- and power, nothing.
anyone have any clue how to recover from this?
Click to expand...
Click to collapse
Use the tool on the lenovo website: rescue_and_smart_assistant_v5.3.0.21_signed_setup.exe
You can restore your OTA
Have you tried this?
https://forum.xda-developers.com/showpost.php?p=83830169&postcount=34
It's a year later... I'm having a similar issue. Were you ever able to resolve the screen problem?
Chaser