Hello, i tried to update the OS manually on my Desire 610, unfortuneatly i guess i soft-bricked it. I can not get out of Fastboot/Hboot menu. Is there any way to get a working OS on it? Or it is trash now?
Some info:
1. TAMPERED UNLOCKED
2. Fastboot devices : good ; adb devices: not found (tried with original cable, every usb slot, millions of drivers)
Code:
C:\Users\Erik\Desktop\fastboot>fastboot devices
HC46NWS01827 fastboot
C:\Users\Erik\Desktop\fastboot>adb devices
List of devices attached
3. I have no TWRP or CWM. Yes i tried to get twrp via fastboot, but it is doing the same.
Code:
C:\Users\Erik\Desktop\fastbo
target reported max download
sending 'recovery' (11588 KB
OKAY [ 1.342s]
writing 'recovery'...
OKAY [ 0.628s]
finished. total time: 1.977s
4. Tried 2 different RUU, but at 1% it throws back an error.
Can some1 help me?
flash stock recovery with fastboot and use recovery to format. I was having the same issue with my 610.
Related
OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Try to create a Thread in the One Plus X Section .
OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
I want to install lineageOS on my Xperia Z5C (I followed these instructions: https://wiki.lineageos.org/devices/suzuran/instal) . The problem is that my phone won't boot into recovery (bootloader is unlocked), after I flashed the recovery onto the phone (I downloaded the suggested recovery file from this page https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050) .
Flashing the recovery file on the phone seems successful to me, because in the Terminal this is displayed:
sh recovery recovery_v3.2.3_22.08.2018.img
target didn't report max-download-size
sending 'recovery' (17352 KB)...
OKAY [ 0.821s]
writing 'recovery'...
OKAY [ 0.180s]
finished. total time: 1.001s
I tried to boot into recovery with all 3 methods known to me: with key combination power on + volume down; via adb with adb reboot recovery and with the quick reboot app. Every time the phone is just booting into android again.
I tried to find people reporting the same problem but I was not really successful.
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
JonSchnee777 said:
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The "fastboot boot twrp.img" command didn't work for me either, but the keystroke to do a "factory reset" -- which is really a keystroke to enter recovery -- did work. Specifically, I
powered down the LG G5 completely (nothing attached to the USB-C port, or battery pull)
with the power off (preferably via battery pulled), held down the Volume Down and Power/Fingerprint buttons
As soon as the LG logo appeared, released and re-pressed the Power/Fingerprint button, all the while continuing to hold down Volume Down
Held down both while the LG logo showed, releasing them after the white screen appeared asking whether you want to do a full erase. Answer yes (Press and release Volume Down until the Yes is grey, then press Power/Fingerprint button)
It prompts you once again. Answer yes again the same way.
At this point after a few seconds, TWRP starts. It hasn't actually done an erase.
This is important: after fastboot flash recovery twrp.img, you need to pull the battery to power down, and then follow the instructions above to enter TWRP. Do not boot into system with the stock ROM after fastboot. It will replace TWRP with the stock recovery at boot time, and in that scenario, the full erase mentioned above actually does erase data and internal storage.
TWRP will on first start change the system image (once you "allow modification") so that the stock ROM stops replacing it at boot time.
If you did boot up the stock ROM after fastboot, you will need to re-enter fastboot and flash TWRP again (power down with USB-C port clear, hold down Volume Up, insert USB-C cable, fastboot flash recovery twrp.img). Then pull the battery with fastboot still running, then boot into TWRP as above.
Unfortunately most writeups aren't crystal clear about the correct sequence of steps. Most cover some steps and gloss over others.
You aren't doing anything wrong.
LG did not put the typical Fastboot commands into the bootloader.
Fastboot flash does not work either.
You need to follow the other methods available on xda to get TWRP on your device.
Edit: woops. That's only with H830. Follow the instructions in the H850 TWRP thread.
Sent from my LG-H830 using Tapatalk
Hi guys.
New to the forums. I know that there are three threads that already detail what I am asking for. I just don't get it. I try to follow one of them and it says "run Qfil; install QPst." I would be happy to do that, but I just do not know where they are or how to run them.
Then one of the twrp files (whatever that is) has been taken down because of "gross violations." I cannot figure out how to do what the threads say to do.
Can someone please tell me how to root this thing? Step-by-step. With all the downloads. Thanks for your help.
Feel free to close this thread when a response appears.
Can someone please respond to this now that it is in the correct forum?
@wsmyth
May be this detailled guide helps you: https://www.getdroidtips.com/twrp-recovery-unimax-umx-u683cl-root/
Good luck.
Thank you
Thank you very much. I am starting there!
Help
I followed all instructions. I cannot get a twrp to load.
Good instructions, but I had these problems.
1. There is no link to a TWRP file. I use the link shown, and I get "Stock April Patch" from mediafire. None of the files here have TWRP in the filename.
2. I did go to https://rootmygalaxy.net/root-twrp-umx-u673c, a similar site. It did have a link to a TWRP file to use. Your instructions are identical.
So I turn off the device. I turn it on with power and volume-up button. The device goes to Mr. Android lying down with the message "No Command." I look at some other sites, and it tells me to hold power, and press power-up.
This takes me to Android Recovery menu. On Windows cmd line (ADB and Fastboot folder), I type adb reboot bootloader. The Windows screen responds no device/emulators found.
So I select option on the Android to Reboot to Bootloader. The device boots into FASTBOOT MODE with START at the top. I imagine that this is what the above command is intended to do. For fun, I type the same command above in Windows, and I get the same response. But when I type fastboot devices , I get the device serial number (as shown on the START screen) and the word fastboot.
I imagine the device is ready to install TWRP. I use the TWRP file that I downloaded from the other page (remember, yours and their instructions are identical). I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Any help is GREATLY APPRECIATED.
wsmyth said:
I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Click to expand...
Click to collapse
IMO you didn't do anything wrong.
To me it seems that OEM/Carrier did not put the typical Fastboot commands into the boot-loader.
BTW:
To test the TWRP recovery without permanently flashing, run the following:
Code:
fastboot devices
fastboot boot twrpname.img
Follow up
Thanks. When I type that code, I get...
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.646s
Thanks again
Does it matter that I have no SIM card in this device. on the START screen, I have this...
Press volume key to select, and press power key to select
FASTBOOT MODE (in red)
PRODUCT_NAME - MSM8909
VARIANT - QRD eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - a10b7526
SECURE BOOT - disabled
DEVICE STATE - unlocked (in red)
Is there anyone that can help me on this? Should I take a magnet to the back of the device? Would that help?
UMX U683CL root?
hey guys, when it comes to all of this i would say i am beyond a newb. so if i violate any protocol i plead ignorance and hope that you will bear with me. i have my disable sister who lives with me and i am responsible for who has had a...
forum.xda-developers.com