I have managed to get the PCeU Ransomware onto my Tab and now when I turn it on i immediately get the splash page asking me to pay up.
No matter what i do to try to get into Safemode or Recovery Mode it is no good I simply get the splash page up which prevents me getting any further in my attempts to remove it.
Any suggestions would be gratefully appreciated.
I forgot to add that the usual method of getting into recovery is as far as I know the power button and volume up after turning the device off first (I have tried up and down volume as well)....i feel however that the device never completely turns off as when I hit the turn off option on the lock screen it shuts down but i dont feel the vibration that i used to get when it did this.
Trasnadunta said:
I have managed to get the PCeU Ransomware onto my Tab and now when I turn it on i immediately get the splash page asking me to pay up.
No matter what i do to try to get into Safemode or Recovery Mode it is no good I simply get the splash page up which prevents me getting any further in my attempts to remove it.
Any suggestions would be gratefully appreciated.
I forgot to add that the usual method of getting into recovery is as far as I know the power button and volume up after turning the device off first (I have tried up and down volume as well)....i feel however that the device never completely turns off as when I hit the turn off option on the lock screen it shuts down but i dont feel the vibration that i used to get when it did this.
Click to expand...
Click to collapse
Try to force reboot recovery by using "adb reboot recovery" and wipe data and cache from here. If you want you can save data from TWRP
Greets
If you can get to download mode and reflash stock rom, it might work!
Cant get to download mode unfortunately. Is there any idiots guides for instructions for "adb reboot recovery"?
Scratch the above.. I found the above and was able to run the command prompt but the device does not appear to be found and when any command is run i get error: device '(null)' not found.
I can see the files on the device in Windows explorer however so would have assumed the drivers when correct.
I suspec the issue is that I cant get into usb debug because i cant get past the blasted ransomware splash screen.
Trasnadunta said:
Cant get to download mode unfortunately. Is there any idiots guides for instructions for "adb reboot recovery"?
Scratch the above.. I found the above and was able to run the command prompt but the device does not appear to be found and when any command is run i get error: device '(null)' not found.
I can see the files on the device in Windows explorer however so would have assumed the drivers when correct.
I suspec the issue is that I cant get into usb debug because i cant get past the blasted ransomware splash screen.
Click to expand...
Click to collapse
Hard boot into recovery and then factory reset. Vol Up + Power until screen pops up then keep holding just volume up.
Related
I was in a bootloop because of a failed ROM flash, however i could enter Download Mode and i used Kies3 to initialize my device and that brought me back to a working system (COI9) But now I have a serious issue, I don't have a download mode?
When rebooting, holding the combination does nothing, just continues me into Windows (Volcume Down + Power + Home) Recovery is accessible, but its the stock Samsung recovery, the option to 'Reboot into bootloader' also doesnt work, my S6 just starts up normally.
Is there a solution for this? I need Root and Xposed back, what should I do?
If you can enter Recovery mode, you must be able to enter Download mode. Usually it is the other way round and people cannot enter Recovery mode. See if your buttons are working properly. Press all buttons (Home, Power and Vol UP + Vol DOWN) then when the screen goes black, try pressing the combination for Download mode.
I 'did' try everything, it was as if the boot loader access was blocked, the ONLY way I could get in was through the "ADB Reboot Download" command, and still then it wasn't the "full" download mode I was use to, it had no info.
I genuinely lost access to it, wasnt able to get in what so ever
Pedroc1999 said:
I 'did' try everything, it was as if the boot loader access was blocked, the ONLY way I could get in was through the "ADB Reboot Download" command, and still then it wasn't the "full" download mode I was use to, it had no info.
I genuinely lost access to it, wasnt able to get in what so ever
Click to expand...
Click to collapse
You mean it goes into Download mode when you try through ADB but it has no writing, is the background still blue and still says something like "downloading target" or whatever it says in Download mode. If it like that, then try see if odin recognises it.
Yes I have succeeded now, its back to working, but in still baffled as to why and how it happened
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
xymic said:
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Click to expand...
Click to collapse
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
xymic said:
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
Click to expand...
Click to collapse
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Mr.Ak said:
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Click to expand...
Click to collapse
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
xymic said:
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
Click to expand...
Click to collapse
Click "Thanks" button
I tried rooting my Pixel 3 tonite and was having success following along with the directions up to the TWRP part. I was able to get it onto my Pixel by typing the fastboot boot twrp-3.2.3-0-blueline.img.
Once the screen popped up on my phone it asked for a password, i just typed in one I use for most things and it went to another screen. I can't remember what i clicked on there but it rebooted and now I get the "your device is corrupt,it can't be trusted to work properly screen.
I can get it to go off that screen by holding power and volume down and I get to the fastboot screen but my platform tools doesn't recognize the device.
I think that is because I clicked of the allow USB debugging right before i did all this because I thought i had it done.
Anyone know if I can get out of this somehow?
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger
I have a pixel 4a with stock rom and recovery that is boot looping after an update. The device has a couple pictures I would like to recover and I was hoping I could use adb to pull those files from the device. The device does have a passcode that I know and and I am able to boot into resuce mode and run "abd devices", and it shows the device in rescue.
When I try to run, "adb shell ls, I get "error:closed"
I tried abd pull "/sdcard/DCIM" and received, "adb: error: connect failed: closed"
Any help is greatly appreciated!
This might be an obvious question, but have you tried booting up in safe mode?
JohnC said:
This might be an obvious question, but have you tried booting up in safe mode?
Click to expand...
Click to collapse
I read holding the power button and tapping the logo was the shortcut but that did not do anything. How do you boot it in safemode?
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Edit: Important: Safe mode removes some Home screen widgets.
JohnC said:
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Click to expand...
Click to collapse
I found that as well and just tried it a dozen times and I never get any safe mode idication at the bottom the screen. I only get a Google logo with a progress bar that never finishes.
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
JohnC said:
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
Click to expand...
Click to collapse
Its running Android 11
It shows 11/RQ2A.210305.006/7119741 in recovery mode. It would have been up update pushed just before 4/4/21. I think it was security updates but I do not know how to verify that. My other Pixel 4a phone updated last around that same time and shows 11/RQ2A.210405.210305.005
This unfortunately is now outside of my experience, so I would be just guessing at this point.
So I was able to get into fast boot and use the flash utility provided by Google and Google chrome to detect the device, but when I try to flash it with sunfish i get an error about "oem unlocking" but I will have to dig further tomorrow. Hoping that I can get it to do something.
That error might be because your bootloader is locked, so it can't flash a new boot image to it.
The only way I know to unlock it is from the developer options in the settings, but that would require the phone to be able to bootup.
Adb sideload the stock OTA in recovery
Glad to hear that