Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command
OmanGhost said:
Hello,
I have OP8 and its was rooted before, I did oem lock from fastboot then I got this message. " your device is corrupted and cannot be trusted"
i can't even flash stock rom. fastboot not accept command
Click to expand...
Click to collapse
Sounds like the bootloader was modified, which breaks the digital signature.
Try unlocking the bootloader again and reboot. Go into developers options and turn usb debugging on. Then connect a cable between your computer and the phone. An RSA signature key should be presented. Check the box "always accept from this computer". Then try rebooting into fastboot and flashing stock.
Not sure of this will help but that's the best advice I can offer.
Cheers,
B.D.
Related
After messing around with my shield last night and not being able to get root access on cm12. I tried to reinstall one of the ota updates from a while back. Now I am bootlooping and when I try to boot into CWM it looks to be corrupted and doesn't load. I cant use ADB because usb debugging is no longer active. Does anybody have any suggestions to re-install recovery or somehow enable debugging or am I dead in the water here? Any help would be greatly appreciated
Is your bootloader unlocked?
Can you get into fastboot mode?
HW method:
Turn off the device
Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
Click to expand...
Click to collapse
If you can get into fastboot mode and your bootloader is unlocked, you can use a command like "fastboot boot recovery.img" to have the device boot a recovery.img from your computer without flashing anything.
If you can get into fastboot mode, but your bootloader isn't unlocked you could try unlocking your bootloader, but this will wipe your data - so only try this if you don't have anything important saved. The command is "fastboot oem unlock".
~Troop
The bootloader is unlocked Whenever I try fastboot mode the device is not recognized because USB debugging is disabled .
Update: Fixed
Ive downloaded all nessecary files.
Clicked OEM unlock and usb debugging
My phone is recogniced in fastboot. When in typing
Fastboot devices and adb devices.
But when i go to bootloader it seems like it not recognice it just says "waiting for device"
What can possibly be wrong ? Im a flashaholic so i need to flash å rom now ?
PS hope there Will be any aosp rom for this device in future
Hello,
is it possible to enable USB Debugging via Fastboot, or reset phone? Think the Partition is bricked...
Bootloader is locked, Phone in Bootloop, Recovery will not start...
Pixel
Oreo
I try to erase via Fastboot...
fastboot erase cache
Erasing 'cache'
FAILED (Write to device failed (Unknown error))
i try 3 USB Cable...
It seems, i must "Enable OEM Unlocking"...
can i do this in Fastboot???
any help?
V-Ripper said:
Hello,
is it possible to enable USB Debugging via Fastboot, or reset phone? Think the Partition is bricked...
Bootloader is locked, Phone in Bootloop, Recovery will not start...
Pixel
Oreo
Click to expand...
Click to collapse
How did you brick your phone. What happens when you choose recovery?
Arju said:
How did you brick your phone. What happens when you choose recovery?
Click to expand...
Click to collapse
After Flash Stock Rom with "Tool all in one" there´s a Question to Lock the Bootloader. I clicked yes ...
When I´m in Fastboot and select Recovery the Phone will start new, but only shows "GOOGLE" for 0,5sec, than black screen for 20sec, again "Google" for 0,5sec,...it repeated for 10minutes
Same when I will Start the System.
Only Fastboot Mode shows correct.
I found this:
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
here you can find the youtube link:
youtube.com/watch?v=5rfk-NtWIIs
and there is The QQ Adress from yingll
qq:247830063
It cost 50$ but my Phone worked...
greetz
Hi,
I have a new X95 with Android 10 go edition. aperently I get an error message when I use some apps.
do not disturb access this feature is not available on this device
Is there anything I can do, to solve this problem?
I would like to flash another img file to the device but got all the time <wating for device> any solution for that?
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
tennoguchi said:
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
Click to expand...
Click to collapse
Use only this command:
Fastboot flashing unlock
I too want to unlock, root and customize the X95... And failed at the very first steps.
I hope some of the forum gurus watches this phone/thread
Here's the steps I took and the errors I got, any help would be appreciated!
1. enable "OEM unlocking" in development options
2. adb reboot fastboot
3. a) fastboot flashing unlock FAILED (remote: 'Unrecognized command flashing unlock')
3. b) fastboot oem unlock FAILED (remote: 'Command not supported in default implementation')
Also, this phone seems not to be recognized in bootloader mode (displays only "=> fastboot", but fastboot doesn't recognize any device).
When booting to recovery, entering fastboot from there (same as after "adb reboot fastboot"), I can get to the point of failure above.
I'm really uncomfortable with the current setup, any help would be appreciated!
Someone got root
Someone got root.
Thank you.
gatolocox said:
Someone got root.
Thank you.
Click to expand...
Click to collapse
This answer/question (?) is not really helpful, can you please elaborate?
Any news on how to root the x95?
Olize said:
Any news on how to root the x95?
Click to expand...
Click to collapse
I haven't tried since the failure reported above, meanwhile I got a redmi note 9s for 119€, so I'm using this one on a custom setup now.
Still using the x95 as an AP, I'm interested on any progress made on the topic..
Hello all
I was wondering if anyone has successfully managed to re-lock a bootloader (on a stock ROM) ?
I got an A51 that I kept as a backup but decided to give it to my aunt instead.
But I'd like to get rid of the the pesky message at boot saying "your bootloader is unlocked, dangerous, blah blah" before I give it to her.
I've flashed the latest stock ROM but it doesn't get rid of that message...
So if anyone has an idea, I'd appreciate it
Try it
adb reboot-bootloader
fastboot flashing lock
or
adb reboot-fastboot
fastboot flashing lock
Edit:
or
How to Relock Bootloader Galaxy A51
Hi, for those of you who have already unlocked the boot loader before, and if one day you change your mind to lock the bootloader again, here's how (remember, This will wipe your data again!) - Shut down your device. - attach the data cable to...
forum.xda-developers.com
Yeah, I tried that already ("fastboot oem factory-lock" for example, as well as some others), but each fastboot command just yields a "< waiting for any device >" message and nothing happens...
And when I try "adb reboot bootloader", the phone reboots in the fastboot mode, but all I get is a message "entering fastboot mode" (or something similar, I can't recall exactly).
Also, when I try sending some adb commands I often get a message saying "
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."