Hello all, I recently started the process of rooting my HTC One X+ and it all went smoothly until it came time to flash a recovery.
I used Windroid Universal toolkit to get started, thinking it would make things easier (not that I haven't rooted a phone before).
I unlocked the bootloader just fine, in the bootloader it gives "*unlocked*".
Next, I tried flashing TWRP with the toolkit, it brings me to bootloader, but when going to HBOOT and hitting recovery, it just brings me back to bootloader. Hmm, weird. So I decide to do it manually, download latest TWRP for evitareul (2.8.5.0), reboot into fastboot.
Execute: fastboot flash recovery twrp-2.8.5.0-evitareul.img
and it gives me this:
"sending 'recovery' (8224 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.153s"
I don't know whether it matters, but when going into HBOOT it pops up with some errors saying something along the lines of unable to access SD or something. It goes too fast to really write it down.
So I think maybe deleting cache would help, and to no avail. I look up online for the error code and nobody seems to have an answer for it. I apologize if this has been answered elsewhere on the forums, I looked for quite some time before posting a new thread. I'm not sure what is going wrong.
My end goal was to flash recovery, make a back up, then flash superSU but if I can't flash recovery then I'm not going to do anything else and risk a brick.
Does anyone know what's up with this error and how to fix it?
You're flashing a wrong recovery.
Coolgoly said:
You're flashing a wrong recovery.
Click to expand...
Click to collapse
What recovery should I be flashing then? My device is Evitare_UL, and I am getting img files from
HTML:
https://dl.twrp.me/evitareul/
.
I have tried other versions to no avail.
Evitareul should only have 2.5 TWRP out....
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
Hello Guys,
I need help with my MiPad 1 (model: A0101).
Earlier, I had Cynogenmod 12.1 flashed which was giving me continuous problems. Today, I looked in the forums after 2-3 years of time to flash another ROM. There I saw devs asking to merge the partitions first before installing the ROM. I started the process of clearing dalvik cache and data via twrp. Then, I flashed the 'Repartition_MI_Pad_1_2GB_zardMi3.zip'. After flashing, the device rebooted to fastboot.
Now, I am not able to move back to recovery and there is no OS installed. I tried flashing TWRP,
fastboot flash recovery recovery-03.11.2018.img
target reported max download size of 645922816 bytes
sending 'recovery' (13626 KB)...
OKAY [ 0.622s]
writing 'recovery'...
OKAY [ 0.391s]
finished. total time: 1.013s
It installs it, but when I try to go to recovery. It comes back to fastboot.
Your help on this will be very much appreciated.
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.
Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1
I only have a linux laptop, so the rescue and smart assistant appears to be off the table
Here's what I did:
Downloaded the boot.img from lolinet
patched it using magisk
flashed it using fastboot
How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.376s]
writing 'boot_b'...
OKAY [ 0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [ 0.350s]
writing 'boot_a'...
OKAY [ 0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.370s]
writing 'boot_b'...
OKAY [ 0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.908s]
writing 'boot_a'...
OKAY [ 0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.949s]
writing 'boot_b'...
OKAY [ 0.525s]
finished. total time: 2.474s
once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo
Any idea what I've done wrong? Would really appreciate some help with this.
Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.
Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
check the forums for the g7 play, I've found topics about that kind of issue.
There's a few touchscreen vendors used for the same device, and they use different drivers basically.
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.
Any idea how to figure out which set is right for my phone?
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
mingkee said:
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
Click to expand...
Click to collapse
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
cnoevl21 said:
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
Click to expand...
Click to collapse
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
mingkee said:
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
Click to expand...
Click to collapse
when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
PamelaGirl said:
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
Click to expand...
Click to collapse
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
PamelaGirl said:
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
Click to expand...
Click to collapse
sadly the phone i tried to root is the only phone that i have
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
PamelaGirl said:
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
Click to expand...
Click to collapse
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
klninja said:
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
Click to expand...
Click to collapse
That’s a good find. Please report back with your success so I stand corrected.
PamelaGirl said:
That’s a good find. Please report back with your success so I stand corrected.
Click to expand...
Click to collapse
a person already did this
That’s good news!
Now its your turn.
PamelaGirl said:
That’s good news!
Now its your turn.
Click to expand...
Click to collapse
i would like to ask a question, when ur g8 wasnt working did the phone charge or not? cus mine dont show how much battery i have
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.