Database Info

Stuck at activation, can't enter recovery, fastboot not working

Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.

md1008 said:
Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.
Click to expand...
Click to collapse
Don't know how I did it, but somehow I was able to go through recovery via bootloader, still curious as to why I wasn't able to before and why installing drivers to enter fastboot mode failed, I am just glad all is running

bootloop and no recovery

Good day.
Thanks fore reading my post.
I had root on my phone like for 3 or 4 months. everything was great and all. I did not dwell in any ROM installing or playing with the firmware.
But I am not sure what I did that this happened.
When I restarted my phone, I experienced everything until the Logo faded to the rotating circle(loading). And it stays there. Always.
I did check on many sites and it seems to be a bootloop. I tried going into recovery, used every button combination possible(I have only 3 and also tried and for my phone and for others to work) and I can't.
It just continues normally and to the position I explained before.
I have a Vodafone Smart 4 Max and even though I want the fix for my phone, I know there are other users that also experience/experienced this problem on different phones.
Might there be a way to fix this?
Thank you for your time
EDIT:: I managed to enter in recovery mode and tried a hard reset of the android. The situation is still the same, the bootloop remaining

Go to bootloader and flash factory firmware with fastboot

I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)

andreinit said:
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
Click to expand...
Click to collapse
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)

minimale_ldz said:
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
Click to expand...
Click to collapse
Hm, I know what you are saying. For me to enter in recovery mode though, I needed to do the following.
1). Fully shutdown the phone for like 30 seconds
2). Volume UP + power button until the first logo with android appears
3). Let the buttons go and I enter
The problem is that adb and fastboot don't see my device at all. I have been tweaking with the drivers for so long, thinking that may be the cause, but I have no results.
And I can use the backup thing to flash a new rom? It requests an update file though, not an image(a zip file)

I think this is about your phone, maybe it will point you in the right direction:
https://www.youtube.com/watch?v=bKHEZbj4NHo

They are figuring out firmware installation on a similair model here: http://forum.xda-developers.com/android/help/stock-rom-vodafone-888-t3002958

LG Spirit hard reset after root is stuck in booting

Hello, so i have a problem. I've installed KingRoot on my LG Spirit H-420 and it worked great, then i searched a bit about this and saw some bad reviews and decided to uninstall it. Then i started searching more and saw some tutorial for rooting with kingroot and then using app called super su-me that uninstalls kingroot and installs SuperSU. So i did this and after installing SuperSU and rebooting my device my signal bar was showing nothing and i was unable to enter settings. Basically when i clicked my settings cog it opened and immediatly closed saying "Unfortunatly settings has stopped working" so i was unable to make calls and access my settings (although i was able to access my wifi/bluetooth/location settings by clicking them in my taskbar). So i unrooted with my superSU and did hard reset by turning off the device and holding vol down and power button to do the factory defaults. After it there was android logo saying working (like always i did the factory reset through my settings) but then its stuck on the boot screen for 30mins, before it hardly took 1min to reset to factory. How ****ed is my device and is there a chance to get it back to working ?

If the bootloader is at least showing the animation, then I don't think you need to worry much. Try the following to begin with:
1. Charge your device for a few hours if it is underpowered.
2. After that, go to your OEM recovery (by long pressing UpVolume + Power buttons) and clear the cache (there usually is the option to do it).
This should solve most issues with bootloop, etc. Try this and report back.

Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.

a7ogpl said:
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
Click to expand...
Click to collapse
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).

prahladyeri said:
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
Click to expand...
Click to collapse
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.

a7ogpl said:
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
Click to expand...
Click to collapse
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?

prahladyeri said:
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
Click to expand...
Click to collapse
The thing i did it and it got into bootloop. If i click yes then there is an android logo with caption "deleting" and then it goes into booting screen [the one with LG Powered by android without animations] and stays like this forever

What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?

prahladyeri said:
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
Click to expand...
Click to collapse
Its saying lg h420 when i connect it and it is in the booting screen (the phone), so i basically could be able to flash it but i dont have my computer and the one here is not powerful enough so i dont trust it. I decided i will just try to give it with warranty and if they refuse then i will flash it. There is no other way now to rvive it. Thanks for help tho

Failed root

Hey,
Tried to root my phone and things got messy.
I'm at a point where when I try to access the bootloader I get the "No command" screen, which I can bypass with the Power+Up keys and reach the "Android Recovery" screen.
I used "Wipe Data/Factory Reset" which didn't help much.
I can't do much more than that because Windows doesn't recognize my device and so I can't apply anything through ADB.
I tried to install the drivers again, but still nothing. My phone doesn't appear on the Device Manager.
Windows does make a sound of connected USB when I enter bootloader, but soon as it hits the "No Command" screen I hear the sound of a disconnected USB device.
Any idea how to make Windows recognize the device again so I could try to install things back with ADB?
Thanks!

OK, managed to solve this part after some reboots.
I'm now failing to ADB the stock image.
The phone says on top of "Andoird Recovery" that it's 7.1.2/NZH54D.
That's the stock image I've downloaded and when I try to ADB it I get on the windows terminal
"cannot read 'sailfish-nzh54d-factory-127f0583.zip'".
How do I move on from this?

OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.

I would start over from scratch. This guide is really good, it's for Pixel XL, but should be interchangable for Pixel 1 (non-XL), just be careful of the model specific files (salefish vs. marlin)
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591

TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
Can't you acces bootloader with "adb reboot bootloader"?
Also make sure u switched on usb debugging in developer options.
Sent from my Google Pixel using XDA Labs

If you get to the screen where you can choose to enter recovery, that is the bootloader. The no command thing is something you always get when you choose to boot to recovery. When on the screen before the no command thing, plug it into your PC. If the PC recognizes it, use fastboot to access it. "Fastboot devices" will show your phone. Adb devices doesn't work there. Bottom line is, it sounds to me you're getting to the bootloader. Just not realizing it.

TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.

Milly7 said:
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Click to expand...
Click to collapse
Yup. I think I'm good now. Gave up on the ROM thing. Too much headache to maintain it. Sticking to stock. Imperfect, but less headaches.
I wanted to root my device mostly for Titanium backup.
The rest isn't that important to me.
Thanks for the help!

Root newbie

Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.

Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no

1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts

Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.

Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4