I have unlocked my evo 3d from htcdev.com. It is S-ON, Non Rooted. I can't flash any ROM, when I enter Recovery it says in the bottom- E:Can't open /cache/recovery/command
When I press "Apply update from external storage" it says then: Invalid operation Success rebooting by reason 0em8 (or smt like that)
update stock rom
Mine stock rom is already in latest Android 4.0.3 dont have any more updates. And its stock. hboot 1.53.007 S-ON Unlocked
Try changing recoveries. I like 4ext.
Read, Search, Read again, ... Then Ask with Tapatalk 2
I said that my evo 3d isnt rooted!! I cant use 4ext! What now? Its just Unlocked so I can flash rom, but Recovery doesnt allow!
twingle said:
I said that my evo 3d isnt rooted!! I cant use 4ext! What now? Its just Unlocked so I can flash rom, but Recovery doesnt allow!
Click to expand...
Click to collapse
Ummm, excuse me, but yes you can. Being unlocked allows you to flash a custom recovery. In fact the order is unlock, flash custom recovery, flash custom Rom. So, you can use fastboot to flash a custom recovery.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
Ummm, excuse me, but yes you can. Being unlocked allows you to flash a custom recovery. In fact the order is unlock, flash custom recovery, flash custom Rom. So, you can use fastboot to flash a custom recovery.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Now I get it. Trying now to install 4ext
twingle said:
Now I get it. Trying now to install 4ext
Click to expand...
Click to collapse
Ok. Good luck. You might want to get s-off too as that makes flashing roms easier and less likely to bootloop.
Read, Search, Read again, ... Then Ask with Tapatalk 2
LOL NOTHING CHANGED!!! XDDD The same problem is in my phone all the time. I tried flashing 4ext, even a official recovery. Maybe its by an error, that i get in cmd?
Code:
C:\Users\aser>cd c:\Android
c:\Android>adb reboot bootloader
error: device not found
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)...
OKAY [ 1.326s]
writing 'recovery'...
OKAY [ 4.644s]
finished. total time: 5.975s
c:\Android>fastboot reboot
rebooting...
finished. total time: 3.370s
c:\Android>
Take a look
You need to root to flash
Sent from my PG86100 using XDA Premium HD app
Related
***unlocked***
shooter xc ship s-on RL
hboot 1.50.0000
radio -0.97.10.000
emmc-boot
aug 7 2011
I have a hand me down Sprint evo 3d that I believe has the HTC dev unlock. I attempted to install the following OTA update.
- OTA_Shooter_S_Sprint_WWE_2.08.651.3-2.08.651.2_release_2201598na37g8l1af4e904
The phone restarted during the update and went to the exclamation screen with the blue android guy. I can get into hboot but when I try to get into recovery the phone boot loops again.
I have been reading for hours and have found several suggestions but do not know where to go from here. From what I can tell I need to re-flash a rom and/or flash a recovery image but but I am not sure exactly what versions of either is needed, where I would get it or if any prior steps are required due to the phones current configuration. I am also not sure how to complete this as from what I can tell, I may have trouble due to the 1.5 boot loader. As much as I would like to try a few things on my own, I don not want to cause more damage or more work for myself.
A few notes.
- I am using a MAC
- I have the android SDK installed but am not familiar with any commands.
- I do not know what version of android I had installed prior to the attempted updated other then I am sure it was a stock HTC load.
- I have not done anything other then try to load recovery since the boot loop
- I can not locate a back up on the SD card.
- I have access to a external SD card reader
- I have access to a external battery charger.
Any help would be much appreciated.
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
mnomaanw said:
flash stock recovery, lock your bootloader then run the ota exe. But why on earth are you flashing the old gingerbread ruu when ICS is available?
Click to expand...
Click to collapse
I attempted to flash the recover using recovery image you posted in another thread.
mnomaanw said:
Not all recoveries work on hboot 1.50 . I got only two working
First boot in bootloader by pressing volume down+power button, then select fastboot and flash this recovery http://www.mediafire.com/?n72emuv5a1c00sd
after flashing recovery , flash a boot.img from the ROM you want to use from fastboot (sorry dont know mac commands)
And then just follow the steps from step no 6 from the link given below.
You should flash the same ROM(MIUI is used in post below) from which you have flashed the boot.img above.
http://forum.xda-developers.com/showpost.php?p=19967637&postcount=16
necessary file are attached in the post and you should put them on SD card
If the above recovery wont boot ....try the recovery from this post
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Click to expand...
Click to collapse
The phone rebooted back into the boot loop. I can still access hboot but am not able to access recovery. I may be using the wrong method or commands.
Input:
./fastboot-mac boot ./recovery.img
Output:
downloading 'boot.img'... OKAY
booting... OKAY
Here is what I get in the fast boot help menu...
usage: fastboot [ <option> ] <command>
commands:
update <filename>.................................reflash device from update.zip
flashall..................................................flash boot + recovery + system
flash <partition> [ <filename> ]...............write a file to a flash partition
erase <partition>...................................erase a flash partition
getvar <variable>..................................display a bootloader variable
boot <kernel> [ <ramdisk> ]...................download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ].....create bootimage and flash it
devices.................................................list all connected devices
reboot....................................................reboot device normally
reboot-bootloader....................................reboot device into bootloader
options:
-w...............................................erase userdata and cache
-s <serial number>.......................specify device serial number
-p <product>................................specify product name
-c <cmdline>...............................override kernel commandline
-i <vendor id>...............................specify a custom USB vendor id
Do you know if I am attempting to flash the recover correctly? It appears as if it is looking for a boot.img from a rom.
To answer your question, the original goal was to update to ICS. I was not aware that the the phone was dev unlocked and never considered that the OTA would cause a problem. I thought it was odd that the available OTA it offered was GB but wrote it off as potentially requiring a series of sequential updates to arrive at the latest version.
After reading this thread I tried flashing again....
http://forum.xda-developers.com/showthread.php?t=1592922
Input:
/fastboot-mac flash recovery recovery.img
Output:
sending 'recovery' (5068 KB)... OKAY
writing 'recovery'... OKAY
The phone went back into a boot loop. I am essentially back to were I started.
I would assume the above procedure is correct. Other then trying other recovery images, I am not sure where to go from here.
I flashed the CWM image from this link as well with no luck.
http://forum.xda-developers.com/showpost.php?p=19944274&postcount=9
Still no luck here. Does anyone think the problem flashing the recovery has anything to do with s-on? I found this link related to the legend and think it may apply.
http://forum.xda-developers.com/showthread.php?t=1290841
I obviously have not tried it because the linked CWM appears to not apply to my phone and I found nothing on CWM's site that would apply.
I am not specifically looking to go stock. I just would like to get the phone working again. Do I need to get recovery working to flash this? Should I just be looking for rom and using hboot with PG86IMG.zip on the SD card? Any input on this would be very much appreciate.
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
mnomaanw said:
you should not boot the stock recovery , it will never work.
you should flash it to your device. then take the ota .
if it does not work, lock your bootloader after flashing stock recovery , then take OTA.
Click to expand...
Click to collapse
Thank you, I was not aware of that. However, I should be able to flash custom recoveries while unlocked s-on correct? I have tried flashing quite a few custom recoveries and am still unable to boot into recovery using hboot or ./fastboot-mac boot (recovery).img.
I plan on working on it more tonight and if I can get it working I'll be sure to post the resolution for other experiencing the same issue. Thanks again for your help.
I just relocked my bootloader and went back to stock Ill mess with it later but at least it works now.
That is great, thanks for the update. I'll give it a shot after work and report back. I got hung up on not being able to get a stock or custom recovery loaded. I was worried about not using recovery to "clean up" before moving on.
Out of curiosity, what method did you flash your rom?
I used the touch recovery then it went to bootloop so I re locked the bootloader and ran the stock RUU, then updated to the OTA 4.0.
Sent from my PG86100 using xda premium
malicenfz said:
I'm having the same problem, boot loop after trying to flash the new OTA zip from the development section now no matter what ROM I flash nothing works. Do I have to try and relock the boot loader then run the stock RUU?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Did you actually flash the OTA successfully and no roms would boot afterward?
You can't take the ota if you are unlocked. Flash twrp 2.2.0 (directions are on their site), then flash a custom rooted ROM. Since you are s-on, you will have to flash the kernel properly (using fastboot or flash image GUI). I recommend you get s-off.
I would give you links, but I'm on my phone. Google is your friend.
Save the Drama for your Mama with Tapatalk 2
Wow Thanks Guy. I used this method to stop boot-loops with 4.0 Rom and it worked like a charm.
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
More info would be helpfully, firstly what is your hboot? Are you s-on or s-off? What Rom did you flash? You are have issues with bootloops after you flash a rom?
(My evil evo is snake bitten by venom sense 4.1 rom and also infected with THE kernel,don't ask me for help, as I couldn't care less if you phone explodes)
Jaklo said:
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
Click to expand...
Click to collapse
re-read the steps on flashing a ROM...youll find out you need more than just the boot.img file to do it... only time you should have to flash the boot.img is when a new rom is installed but wont boot up...if your phone still boots then youre not installing the ROM properly
You need to supply the information that flashallthetime requested, but you should also be aware that flashing boot.img from fastboot does not flash the ROM and doesn't even flash all the files associated with the kernel. The attached screenshot of the warning that comes up in 4EXT when selecting the "flash boot.img" option expains it better than I can.
If you are S-ON, the proper way to flash a ROM is to "fastboot boot recovery.img" then flash the entire ROM .zip file from recovery, or use 4EXT with the S-ON (SmartFlash) option enabled. You can tell that SmartFlash is working by watching to see if your phone boots twice after your exit recovery. The first boot is used to flash the boot partition and the second boot loads the new kernel and ROM.
Don't confuse the complete kernel with boot.img, which is only one of the files required.
ramjet73
thank you for your replies!!
flashallthetime my hboot version is 1.53.0007 and i am s-on.
I tried to flash the Cool-ICS and the cerom.
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Jaklo said:
thank you for your replies!!
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Click to expand...
Click to collapse
I'm not familiar with the S-ON flashing guides for GSM which will be a little different than those for CDMA, so someone else will have to help with that, but you can get the recovery.img file for 4EXT that you need from the OP of the XDA thread. It's right above the other download links on that page. Look for the following sentence that has the download link embedded:
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
Click to expand...
Click to collapse
ramjet73
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
EM|NEM said:
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
Click to expand...
Click to collapse
Thanks again for the quick replies!!!
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix the hboot problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Jaklo said:
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix those problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Click to expand...
Click to collapse
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
i know that i have to be in fastboot usb mode
it gives me cannot load recovery.img error.
Buuuuut i finaly managed to install yoda´ s ICS custom ROM and EVERYTHING workssss
THX guys
Theres no way to downgrade your hboot without the wire trick my friend. you need s-off to downgrade your hboot. any older hboot could have easily been downgraded and then s-offed
I would suggest you try some other rom. This ones a pretty good rom (sense 4.1 but no 3d) and i'm sure it works with s-on/1.53
http://beta.androidfilehost.com/?fid=9390113915771289764
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
---------- Post added at 03:50 AM ---------- Previous post was at 03:46 AM ----------
oh good you already did another rom. good for you
EM|NEM said:
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
Click to expand...
Click to collapse
ok sorry for a noob question but does wipe mean factory data reset?
that is what i meant. do factory data reset and wipe dalvik cache as well
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
The OP cant load his recovery because he might not have a file named "recovery.img" in his fastboot/adb folder.
Flashing a boot.img is just the part of flashing ROM, especialy on S-On state. It still has not flashing your ROM, until you "update from *.zip file" from recovery.
Resolved: I had mistaken the stock recovery screen for an error screen. Noob error.
Hey there,
New ATT One X+ user here. First off, wanted to say great job to all the devs! Exciting to see so much progress.
Anyway, I successfully unlocked my phone, flashed TWRP, and installed Elegancia ROM using hasoon2000's tool. Now I would like to revert to the stock recovery, since offmode charging doesn't work for the ATT TWRP yet. However, I'm having an issue: I can't flash a stock recovery back onto my device! (When I try to boot into stock recovery, the red triangle with a "!" pops up)
Here's an outline of what I tried:
1) grabbed the ATT stock recovery from http://forum.xda-developers.com/showthread.php?t=2064295
2) renamed the recovery "recovery.img" and put it in the folder where my fastboot is
3) flashed the recovery using "fastboot flash recovery recovery.img". It looks like it's successful; here's the output:
" sending 'recovery' (7142 KB)... OKAY [ 0.922s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.389s]"
4) tried booting into recovery, but it shows the red triangle error screen
Now, if I follow the above steps using the TWRP recovery image, I am able to boot back into TWRP. It's odd that the flashing works with TWRP but not with the stock recovery...
Other potentially useful troubleshooting info
- I tried using hasoon's tool to flash the stock recovery, but it has the same results
- my bootloader still says it's "UNLOCKED"
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)" (nevermind, command doesn't work in S-ON state)
Thanks in advance for any help!
kproto said:
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)"
Click to expand...
Click to collapse
does not work at S-ON state
skdubg said:
does not work at S-ON state
Click to expand...
Click to collapse
Had a feeling that was the reason, but thought I'd include it just in case it was relevant to the problem. Thanks, will edit original post
Iam wondering too... So how to make this? Any special procedure? To flash back stock recovery?
Wysyłane z mojego HTC One X+ za pomocą Tapatalk 2
kproto said:
Hey there,
New ATT One X+ user here. First off, wanted to say great job to all the devs! Exciting to see so much progress.
Anyway, I successfully unlocked my phone, flashed TWRP, and installed Elegancia ROM using hasoon2000's tool. Now I would like to revert to the stock recovery, since offmode charging doesn't work for the ATT TWRP yet. However, I'm having an issue: I can't flash a stock recovery back onto my device! (When I try to boot into stock recovery, the red triangle with a "!" pops up)
Here's an outline of what I tried:
1) grabbed the ATT stock recovery from http://forum.xda-developers.com/showthread.php?t=2064295
2) renamed the recovery "recovery.img" and put it in the folder where my fastboot is
3) flashed the recovery using "fastboot flash recovery recovery.img". It looks like it's successful; here's the output:
" sending 'recovery' (7142 KB)... OKAY [ 0.922s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.389s]"
4) tried booting into recovery, but it shows the red triangle error screen
Now, if I follow the above steps using the TWRP recovery image, I am able to boot back into TWRP. It's odd that the flashing works with TWRP but not with the stock recovery...
Other potentially useful troubleshooting info
- I tried using hasoon's tool to flash the stock recovery, but it has the same results
- my bootloader still says it's "UNLOCKED"
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)" (nevermind, command doesn't work in S-ON state)
Thanks in advance for any help!
Click to expand...
Click to collapse
To be polite I would not flash the recovery he linked, While he may have good intentions all of his other posts I have seen and tried to help deal with have shown a lack of understanding and experience with android. For all I know he is hosting the same file I gave him earlier but incase he isn't please download this recovery: https://www.asuswebstorage.com/navigate/s/665115AABBFA49E783795815A6E5666F4 Go into fastboot and flash it using command prompt with "fastboot flash recovery (recoveryname).img" Please note stock recovery should a picture of a phone down with an alert signal above it. Please note this is for AT&T ONLY
Oh! Well, I feel foolish now -
I had thought the screen with the phone down and a red alert over it was an error screen. I assumed there would be some menu options or something on there; are there not supposed to be?
Just to confirm, I've attached a picture of my phone booting into the stock recovery you posted. Is this how it's supposed to look?
kproto said:
Oh! Well, I feel foolish now -
I had thought the screen with the phone down and a red alert over it was an error screen. I assumed there would be some menu options or something on there; are there not supposed to be?
Just to confirm, I've attached a picture of my phone booting into the stock recovery you posted. Is this how it's supposed to look?
Click to expand...
Click to collapse
That is standard recovery menu.......
Kraizk said:
That is standard recovery menu.......
Click to expand...
Click to collapse
Fantastic. I guess I should have checked out what the recovery looked like initially before flashing TWRP over it. Anyway, thanks for all your help!
Any news on S-OFF?
no s-off for Tegra devices....
At all...for sure?
Sent from my HTC One X+ using xda premium
yes!!!!
I was running the latest TRON ROM from Neo with no issues for several days. Tonight, I went to use the camera and it FC'd. It kept doing it so I tried rebooting. It flashed the white screen with the green HTC logo and thats it, it won't go any farther.
I can get to recovery by pulling the battery and using the hard buttons, but recovery is not able to mount the internal or external memory. I cant backup, restore, flash a zip, or do anything really. How could this have happened? Am I bricked?
HELP!
If the phone does anything at all, it is not bricked. (The state it's in is sometimes called a soft brick, though). I believe there are two things you can do: either get an RUU (PH98IMG.zip) onto your SD with a computer (and an SD card reader EDIT: Or the Incredible you mentioned in the ROM thread), then boot up to hboot and let it flash, or try flashing a kernel (boot.img), ROM, or RUU using adb/fastboot.
If you have questions about the first of these processes, I may be able to answer them, but I probably won't be too helpful about the latter since I haven't flashed anything with adb/fastboot in quite a while.
HERE is the latest RUU, by the way.
Thanks, I'll try this out tomorrow.
s-on? Can you boot into the bootloader? Try reflashing the kernel via fastboot.
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
Did you re-unlock after running the RUU?
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
download this zip and place it on the root of your sd card. it will flash Amon RA through hboot. no need for fastboot commands.
http://androidfilehost.com/?fid=9390248398092764223
mjones73 said:
Did you re-unlock after running the RUU?
Click to expand...
Click to collapse
Just realized that, after doing some research...DOH!
Unlocked and good to go. Thanks!
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....