guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
Related
Hi, I am remotely helping my friend to recover data from his phone. His phone is broken and usb debugging is disabled. So I asked him to reboot to recovery (for adb support )which he cant as the phone is restarting (confirmed this from windows 7 autoplay ) , he was able to boot to fastboot. Now how to reboot to recovery, he is unable to remember which recovery he is on. He is on CyanogenMod lollipop. How to reboot to recovery. Thanks
Finally did booted to recovery but adb says unauthorized. Anyway mtp is listing the folders
When I was trying to root my P10 I was trying to install SuperSU via TWRP but my file names were crypted, and I couldn't find the .zip file.
After some research I found out that it's a common problem, and can be solved by flashing a custom rom (no-verity-opt-encrypt.xxx.zip)... And that is supposed to decrypt the filenames.
After sideloading that file, I can't boot my phone as I get stuck on a screen saying: "your device is booting now..."
I can get to huawei eRecovery by pressing the volume up - I can't do a factory reset, it just says your device is not supported.
I can also get to fastboot & recovery mode screen, and by typing "fastboot devices" in console I can see my device's number so I can acces it.
If I type fastboot flash recovery twrp-3.1.0-0-P10.img it would successfully fiinish but it wont do anything.
Can I somehow fix this?
EDIT: saved the phone with
https://forum.xda-developers.com/p10/help/model-t3713886/post74719465#post74719465
I updated my oneplus and i got the TWRP decryption message, so i formatted it back to the stock format.
now all the phone does is boot into the bootloader but gets stuck on the boot screen of Blu Spark 3.1.1
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
is there anything i can do or is my phone screwed at this point? i see a lot of threads that would answer parts of my issue but nothing that covers this as a whole. id rather ask for help now while there may be some hope.
nickhawkjones said:
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
Click to expand...
Click to collapse
So no response to fastboot commands, while in bootloader-fastboot mode?
Are you sure you installed the right drivers for your pc? If all else fails, you can do this.
This is how I fixed my phone when i was stuck at a black screen. You can also try a different usb cord or port. Check device manager and see if it recognizes it when its plugged in. hope this helps!
https://www.youtube.com/watch?v=BvfA5WrVDQM
can you boot into fastboot? if your phone can boot to fastboot mode..just flash stock recovery image..then flash rom via adb shell (better flash the stock rom). if it works you can reinstall the custom recovery image or something. dont forget to erase everything via stock recovery..
Hi,
I'll start by saying this is the first time i've tried putting a custom rom on a phone.
I unlocked the device, enabled usb debugging and installed twrp. I was able to get into recovery mode and wiped the correct partitions.
I was then unable to install pixel experience? I was unsure how to put the rom on the phone. It was not coming up on my pc when connected.
I then disabled MTP and rebooted the phone. It went straight to fastboot and no matter how many times i reflash twrp, or what button combinations i push, i'm stuck in fastboot.
Can anyone help?!
Thanks in advance!
A helpless noob
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus