I purchased an HP Slate Pro 21 off of ebay that was freezing on boot, and it definitely is. My thought was if I could unlock it and load a different ROM, etc. that the problem may go away. Here is what I have done/figured out so far.
First power on, the device freezes at the first HP logo.
wiping the data (factory reset) allowed me to get into the O/S after several reboots
I was able to enable developer mode and USB debugging, at which point the device forces a reboot.
From this point, no matter what I do I cannot get the device to boot up all the way without freezing.
I can however, reload the factory image from HP's site (tried via SD card, and ADB just in case) and eventually through a multitude of reboots and freezes in different places (i.e. Boot Logo, Animated Boot Logo, Optimizing Apps) it will boot into the setup menus.
Problem is, at this point USB debugging has been factory reset to disabled. If I enable it, I'm back at square one and can't get the device to fully boot up.
There is a menu option to deploy image via ADB, and I can connect to it from my PC but it's (I believe, since I'm a noob) that it's a restricted mode for sideloading only.. Since I can see the device in the device list but it says (sideload) next it and the only adb command that I can run is to transfer an image. Problem is, I only have the HP image.
Are there any other steps to determine if this is a hardware problem? Further things I can do to try and get the device to boot? Other images I can try from ADB or SD Restore that will pass the signature check? (Since I can't load TWRP yet, because it's still locked).
Thanks for any help you can offer!
Related
I've come across a problem that's frustrating me to no end. I've been rooting phones for a few years now, usually older models. A friend asked me to root his newly aquired S6 (canadian model, eh), shouldn't be an isssue. I do the standard issue Enable Developer, wipe data/cache, install root and rom, and call it a day. I go to reboot it, and it's in a boot loop for the Samsung screen. I've had boot loops occur before, I'll take care of it.
I've been at this all day (10+ hours), and still don't have a way to escape this boot loop. Problem is that I didn't know about the Reactivation Lock that was still active when I attempted to root. Here' what I've attempted:
- Uninstall/Reinstall USB drivers several times and different versions. Phone will still not show up under ADB Devices and not detected by windows or toolkits (but will still register via Odin).
- Restore from backup: will only boot into stock recovery mode, no option for restore.
- Reinstall Firmware via USB OTG - "USB access is disabled"
- Install other roms, always fail or are denied access
- Update/Change kernel , see above
I could list on and on all the little tricks and toips i've tried from the internet, but what it essentially comes down to is I can't install anything onto the device due to the device not being recognized or being blocked by a permission, and yet I can't get into the actual Android OS to disable/Enable any permissions. Factory reset does not fix this loop, nor does clearing caches. I've tried sideloading, pushing, and various other means to get into Android, but nothing is working. Help?
Hi, Please help! So on the final day of a 15 day Himalaya trek my phone downloaded and installed the November update. after this the phone would no longer boot just staying on the G loading screen. As I was in the mountains there was no WiFi so the photos hadn't been automatically backing up and I am unable to access them at all now.
Steps tried:
1) restarting device multiple times to access alternate boot (this didn't work).
2) sideload with latest OTA Image (this just did the same thing, stays on the loading screen)
3) Leave phone on loading screen (did this for over 48 hours no change)
4) Contact Google support (did this they said only fix was to factory reset the phone.... NOT HELPFUL!)
look into 3rd party application on windows and mac to access the internal storage (none could see the phone)
5) Unable to sideload a previous version of Android due to the boot loader being locked.
phone is not rooted and as unable to boot cant find a way to do it.
Only other thing I have found would be to do the reset and hope that one of the 3rd party apps will be able to retrieve the data once I can boot back into OS.
Or wait for another OTA Update and try that.
Any help greatly appreciated.
flash factory image but remove the -w
I was trying to root my main driver, a Google Pixel 3 running the most recent version of Android. Initially I was going to flash TWRP and then install Magisk, but TWRP for some reason wouldn't flash, so instead I went about trying to go about the Magisk Canary route. I patched the boot image of the most recent Pixel 3 update and proceeded to flash that in the bootloader. That is when everything went wrong. When the phone rebooted, I found that my touchscreen was no longer working. I tried flashing the boot image using platform tools in the bootloader, but I deleted the -w line in flash_all.bat to prevent a full reset; however this did not solve the issue as I had hoped. I then went into device recovery mode and tried the factory reset option there, but that did not work either. The phone booted and I was in the setup screen with no way to press the buttons using the screen, so I connected an OTG USB device to set the device up only to find that the WiFi is not turning on. I believe there are issues with the mobile network as well as I put in a SIM card but it wan't able to connect to the network; however it did read the SIM card successfully as I was able to "turn on" mobile data. I cannot enable USB debugging to flash anything because I cannot allow the computer's USB debugging request; I either have the computer or my OTG device plugged in. Any ideas on what to do? Thank you in advance!
i have almost the exact problem.
could someone please help
Sounds like the option is, factory image flash-all with the wipe. I believe the OP did not disable/remove modules from magisk before updating. That is something that we all should be aware of at this point. Cost me two bootloops and complete resets, but I learned my lesson. Also backup your stuff. I lost a few pictures, but most of my data and such were restored through Tibu.
I switched off my phone (Motorola Z2 force, XT1789-06) during ringing. I am not sure if this caused the problem, but since then I can't switch it on. During booting, when it starts to show the animated "Moto" logo, it restarts booting, so I can't get to the normal graphical user interface. If I don't touch it, it repeats rebooting until its battery gets empty. It is not rooted, has latest official Android (version 9, I think, nash_retail) on it.
Until now the only thing I could do is to boot into fastboot mode. There I can log in into recovery mode or do some diagnostics, check some logs etc. As far as I can tell they show no problems at all. Except maybe "failed to read fstab from dt" in /tmp/recovery.log -- is it normal in recovery mode?
I tried some manual reboots from fastboot/recovery menu (on the phone), with and without SIM card inserted, with and without being connected to the charger, but they changed nothing: the phone keeps rebooting at the same stage of booting.
I hoped to be able to adb connect to the phone and pull the files from it, hoping I could use these data after a reinstall. But adb devices show no connected devices. I guess adb is not available in this stage of Android loading. Or is it available somehow?
fastboot devices show the phone, but I am not sure what can I do without triggering a factory reset. E.g. what if I would 'fastboot flash boot boot.img' from the stock ROM? I guess something went wrong on the boot partition, so rewriting it could solve the issue. But I afraid rewriting the boot partition would result in a complete factory reset.
My questions:
* what to try to make the phone booting normally?
* can I change boot config to skip logo animation?
* if booting normally is not possible: can I somehow copy my files from the phone to my laptop (linux)? If I can copy them: is it realistic to be able to use those files to restore the apps' states after a reinstall (after a factory reset)? I would like to keep e.g. my phonebook, SMS, Whatsapp and Signal chat history, OsmAnd favorites, Colornote notes, AndOTP credentials, etc. (I have a backup of some of my files, like photos or gps tracks, synced to my laptop with SnycThing automatically, but many others are not backed up recently.)
* if backing up my data is not possible: can I try to fix the booting issue by e.g. flashing a new boot.img without risking a factory reset? What exactly should/could I flash?
* if none of the alternatives above work: are there any other thing I could try or shall I simply accept the data loss and do a factory reset from fastboot menu?
Thanks a lot for your help and ideas in advance,
Peter
Hello everyone,
So I have a rare issue. I have a OnePlus 6. Today, it started to act really weird. It became so slow that even swiping on home screen with no apps opened takes like a minute to register. I forced power off the device. When powering on again, it seemed like it take around 10 minutes or so to boot. Again, extremely slow. I tried everything from restarting and clearing app cache while in the system itself but no luck.
So, next thing I booted to recovery mode, typed my pin, and cleared system cache and settings. It started to progress until just a tiny bit left before the end of the progress bar, and it got stuck again. Kept like this for a long time. I had to force power off the device again. Now, when I try to power on the device, it launches into Recovery Mode. I tried my pin but it wouldn't decrypt and looks like the device is no longer recognizing it. I tried a couple of "default passwords" but it wouldn't work either. It only gives the option to "Forget Password?" Which should wipe everything off the phone. The only other mode it launches into is Fastboot Mode. I'm using Stock everything and Device State is Locked. I'm not sure where to go from here.
Now my question is, is there any way I can open my device again without losing data? Maybe some way I can pull files using adb in that state then factory reset? Or maybe someway I can bypass Recovery Mode and boot again? I have important data that I can no longer access if the only way to fix this is by wiping everything!
Can anyone help? Much appreciated in advance.
When a phone permanently boots into Recovery mode then either Android OS is corrupted - for whatever reason - or phone's bootloader is misconfigured.
If phone is accessible by either ADB or Fastboot you can try to exit Recovery mode by forcing phone to boot into Android OS ( Normal mode AKA System ) by applying the related ADB and/or Fastboot command.