I tried to root my Nexus player today. I followed this guide word for word. cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
Everything worked fine until I got to Step 4. I typed in "fastboot boot root.img" and the system rebooted with elevated privledges (unlock logo on boot). Just like the video said the device was wiped and I had to go through the factory setup again. It went wrong when I got back into the home screen. There should have been a superuser app installed. I looked on the home screen and in app's under system, and it was not. I thought it just needed to be manually installed so I downloaded it from the app store and installed. I was able to launch it and I selected "Continue" and "Normal" just like in the guide. However unlike the guide the installation failed, and prompted me to reboot and try again.
After I rebooted, the OS fails to load. The only thing I see when I turn it on is the Google logo, then it just sits at the "4 dot's" screen that should indicate it's booting up. I have no idea what to do and subsequent reboots have still hung at this screen. Please help all I wanted to do was use an external usb hard disk with Kodi.
Related
I need help. I was on stock android 4.1.2 while rooted and unlocked with cwm. I was using it this morning when I got the notification for the ota 4.2.2 I accepted it and the device rebooted. I got a message saying if I wanted to install the update because it wasn't signed. It looked like I was in cwm at this point. I said yes, and it proceeded to try and install, halfway through it just rebooted and brought me back to that screen again. I tried a few times before saying cancel. I was then brought to the main cwm menu, I selected device reboot. It booted into android after a lengthy time, but when it loaded android it's a black screen with the clock lock screen widget, and anytime I try to get past the screen shuts off. I don't have any way of booting into cwm, I can't do it by powering down then powering up holding the volume down button had to use rom manager. Please, any ideas on how to un**** this up. I was able to get my computer to list it in adb devices, but when i typed in reboot-recovery it says android debug bridge 1.0.31 and the lists all the commands. After being connected to the computer for a few minutes it just shuts off and won't turn back on unless I plug it into the wall for a few minutes. If while in adb I type adb reboot-bootlader it reboots but not into the bootloader.
Update, about the 3rd time I tried the adb reboot bootloader it worked, I was able to get into fastboot and flash a stock image, works fine now. No idea how it got so bad from just that though
Ok, my Nexus 7 is stuck - not getting passed from Google boot screen.
Here is a bit of history..
I unlocked and installed Cyanogen 10.1 awhile back, and TWRP recovery. It's actually dual rom - I can't remember the name of the other ROM.
I haven't used it for a few months and today I charged the battery and used it. It was all good until I checked for update and found that there is Cyanogen 10.2.1. So I clicked download and install.
It downloaded, then rebooted. And when the system is up, I got the pop up saying Google Service is stopped unexpectedly. Some app icons I got on my home screen are still there, but there is no menu bar. There is no home button, no app drawer. So I rebooted, and the same google service error.
So I thought, maybe it's not compatible with 10.2. I rebooted into recovery mode and install 10.1 (the old rom zip file was still on the device) using TWRP. Only took a few seconds and then it says successful/done. To make sure, I also did wipe dalvik cache, then reboot.
Now the system only goes as far as Cyanogen loading screen. That's it. So I hold the power button for a few seconds, then when the device restart, pressed the volumn down button. Then I chose 'reboot recovery'.
It doesn't. It just hangs at Google screen. I tried a few times, the same. So trying to reboot into recovery hangs at google screen, and trying to reboot normally hangs at Cyanogen screen.
As a last attempt, I let the screen hangs on Cyanogen log, connected the device to my Mac, then tried "fastboot devices". Nothing.. empty.
But when I tried "adb devices", I get an entry something like this
Code:
List of devices attached
015d2bcxxxxxx unauthorized
Code:
./adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
What should I do to get my tablet working again? I dont mind losing all data - I just want it working again. Someone please advice me..
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Yodhrin said:
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Click to expand...
Click to collapse
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
strongst said:
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Hi, thanks for responding. After four or five attempts to boot into recovery it succeeded; wiping the cache did nothing so I did a factory reset, which worked and now the phone will boot to the setup stage. Unfortunately now I'm getting "The device was reset. To continue, sign in with a Google Account that was previously synced on this device.", which after googling seems to be a security feature - the problem is it doesn't accept the google account credentials, every time I enter them it just cycles back to the "This device was reset..." screen again.
I know I'm not getting the details wrong since I made the account specifically for the phone and have the details written down. Any suggestions on how to proceed?
EDIT: Actually nevermind, I managed to follow along with a tutorial on how to bypass it using MotoService & ADB. Thanks again for replying.
Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.