Related
I have been researching the white HTC screen boot loop for the past 3 days trying to figure out how to fix my Evo3d. After today i have finally given up.
On HBOOT my phone says:
*Locked*
Shooter XC SHIP S-OFF RL
HBOOT-1.50
Steps taken to try and fix:
-Flashed stock RUU and it completes, but reboots into the bootloop
-Upload PG86IMG,zip onto phone. Updates fine and reboots back into bootloop as well
-Don't have a nandroid backup and can't get into recovery anyway. When i flash recovery through CMD i get the message:
sending 'recovery' (4706 KB).
OKAY [ 1.160s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.170s
Not sure what else to do or what to try. Any help would be greatly appreciated.
Thanks
milkycoins said:
I have been researching the white HTC screen boot loop for the past 3 days trying to figure out how to fix my Evo3d. After today i have finally given up.
On HBOOT my phone says:
*Locked*
Shooter XC SHIP S-OFF RL
HBOOT-1.50
Steps taken to try and fix:
-Flashed stock RUU and it completes, but reboots into the bootloop
-Upload PG86IMG,zip onto phone. Updates fine and reboots back into bootloop as well
-Don't have a nandroid backup and can't get into recovery anyway. When i flash recovery through CMD i get the message:
sending 'recovery' (4706 KB).
OKAY [ 1.160s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.170s
Not sure what else to do or what to try. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
you still have to unlock your bootloader.... http://www.htcdev.com.... go to that site and follow the steps to unloack your bootloader... THEN try to install your roms and you should be ok ....
wloftus said:
you still have to unlock your bootloader.... http://www.htcdev.com.... go to that site and follow the steps to unloack your bootloader... THEN try to install your roms and you should be ok ....
Click to expand...
Click to collapse
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
milkycoins said:
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
Click to expand...
Click to collapse
Have you tried to downgrade your h-boot to 1.4? You could use the live CD or unknownforce's method (see my signature).
Sent from my ICS 3VO with Tapatalk 2
milkycoins said:
Tried this and get " error: cannot load 'Unlock_code.bin' " on the last step
Click to expand...
Click to collapse
what operating system on your computer are you using?
and just exactly how are you typing in the command?
wloftus said:
what operating system on your computer are you using?
and just exactly how are you typing in the command?
Click to expand...
Click to collapse
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
milkycoins said:
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
Click to expand...
Click to collapse
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
wloftus said:
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
milkycoins said:
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
Click to expand...
Click to collapse
go to cwm and wipe everything, that's what worked for me
milkycoins said:
Okay so i did this, flashed the boot.img and it said
sending 'boot' (3622 KB)...
OKAY [ 1.013s]
writing 'boot'...
OKAY [ 8.993s]
finished. total time: 10.007s
It completed and didnt do anything. So i just chose Reboot System in HBOOT and hoped it would restart normally, but went back to the HTC loop.
Thank you so much for your help on this i really appreciate it!
Click to expand...
Click to collapse
just like the last post says...try to boot into recovery now...wipe your dalvik cache and then reinstall the rom through recovery ...with the unlocked bootloader and s-off combo you should be ok... post back and let me know... and youre welcome
milkycoins said:
Okay so I got the Unlock code to work and now my phones HBOOT says:
*UNLOCKED*
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50
I was able to then flash ClockWorkMod recovery and install a new rom. The install completed and when i went to reboot...
Same thing happens, white htc screen loop.
Feeling pretty hopeless right now, ha
Click to expand...
Click to collapse
Interesting. You used the HTC unlock method and your phone is showing s-off. I was always under the impression that the HTC method leaves you s-on.
The reason I say that is because your phone is showing symptoms of being s-on. If you use 4ext set to s-on and try to flash a GB Rom, does it work?
Sent from my ICS 3VO with Tapatalk 2
wloftus said:
ok now you take the rom and open it up on your computer and extract the file boot.img
copy it to the same place where fastboot.exe and adb.exe are located
go to your phone and hold in the volume down button and press power to get to your bootloader
select fastboot
then plug it into your computer
open up a terminal window on your computer and go to the directory with fast boot and type in
fastboot flash boot boot.img
Click to expand...
Click to collapse
wloftus said:
just like the last post says...try to boot into recovery now...wipe your dalvik cache and then reinstall the rom through recovery ...with the unlocked bootloader and s-off combo you should be ok... post back and let me know... and youre welcome
Click to expand...
Click to collapse
Man i just tried this 3 times and no luck. I dont know what else to do. This is so wild.
First off, the original thread is here: http://forum.xda-developers.com/showthread.php?t=1950232
It looks like some users are having an issue with the following results:
1. Unable to boot into Fastboot - HAS SINCE BEEN FIXED
2. Unable to wipe/flash from CWM
3. Unable to wipe /cache or /data
We aren't sure if this is a hardware issue or a software issue, but we are trying to figure it out.
I am running Epinter CM10 (from early september), and I hadn't flashed a new version of the rom since then. A couple days ago my phone started giving me a bunch of errors (application crashes) so I decided to update to the latest version and wipe. After wiping, and flashing, I rebooted and everything looked the same. All my applications were still on lancher and all my texts were there. So it clearly didnt work, when I went back into CWM I tried wiping specific partitions manually and found there were errors when trying to format /data and /cache. Trying to reboot into Fastboot it gets stuck at "starting fastboot protocol support", and never is detectable from command prompt.
My first question - Are there any ways to wipe the Atrix outside of CWM and Fastboot? Would flashing a SBF from RSD do anything? (I am already rooted which you probably knew from the fact im running epinter CM10)
Has anyone found themselves in this situation and found a fix?
Thanks for your help.
Firstly, questions go to the Q&A section.
Secondly, I've faced this issue a few weeks ago where nothing happens when I wipe everything and flash a new ROM. But miraculously my restore worked and then everything went smooth after that. I came from Epinter's CM10 as well, I restored to Maxblur I think. Now on MROM, flashing still works.
If you have the time and are desperate to flash something, you can try to SBF back to your previous firmware. Only problem is, you might need to wipe you phone using... fastboot.
I'm not sure though, it might be a hardware issue.. Besides, my digitizer is failing and my wifi disables and locks itself every now and then...
Edit: Reading you post in that other thread, you mentioned that your phone went into "starting USB protocol". Do you have the correct drivers loaded on your computer? Have you tried reinstalling CWM or another recovery?
Sent from that Atrix.
Thank you for your reply. The reason I moved it here was that some others had this issue with epinter and it straddled the lines of Dev and Q&A, and there wasn't much exposure on the Q&A forum and it seemed that others using epinter were having this issue.
1. I will try a restore and report back on if that worked (I tried restoring before which resulted in a failure when it gets to /data)
2. I will double check fastboot is properly installed.
3. I will also try flashing the CWM non-touch version
**Edit**
Update to item 1:
I tried restoring a backup on CWM and got the following log:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while formatting /data!
boot in fastboot your atrix. power on + vol down, then when show fastboot press vol up. then in windows cmd write this commands.
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (reboot to recovery)
Flash ROM.
if doesnt work try with moto-fastboot program and moto-fastboot commands, mine atrix worked fine
try installing another recovery i get this same error its work for me
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
sjbayer3 said:
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
Click to expand...
Click to collapse
I always thought we needed to use moto-fastboot, not just fastboot.
I also used romracers recovery and then Th3Bill's Full_Wipe flashable wipe tool to recover from a similar situation.
Good luck.
Okay.
I found moto-fastboot, and using that STILL nothing gets wiped.
I tried flashing the non-touch recovery, and well it shows everything success... but when I open recovery its still the touch recovery.
It just seems like something is locking me out from doing any wipe or flash to my phone, I am just baffelled that nothing has worked so far.
Trying to format from fastboot and I got this output, type ".FAILED ()" certainly doesn't sound good.
C:\Users\ofsstbay>fastboot format userdata
formatting 'userdata' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.014s
C:\Users\ofsstbay>fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.012s
C:\Users\ofsstbay>fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.010s
In addition, when I flash recovery:
C:\Users\ofsstbay\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-oly
mpus.img
sending 'recovery' (4824 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.125s]
finished. total time: 0.415s
On the phone screen it says:
Flashing partition recovery
Flashing StorMgr partition: SOS
Belongs in Q&A. I closed other one since this has more replies. There aren't any exceptions for organization on the forums. Please do not post questions in Development even if they "straddle the lines." Thanks!
Same issue here! I was on uriels awezome rom when it happened. I've tried fastboot, and even rsd lite wiping everything at once, individually to no avail.
Well I even tried going through the originaly root unlock and recovery flash and still didn't do anything. None of my backups work either still
any one figure this out yet??? I can't think of anything else to try myself.
is it possible that the internal sd is corrupted and possible the data partition as well?
I was thinking the internal card was corrupt as well.
Is this something that can be removed and replaced or is it built into the board?
i looked that up. I saw a different phone where it is removable but not necessarily replaceable. I know there is a way to use the sd card as the internal but the directions are above me. I wish some devs were reading this thread. Doesn't seem like it's got enough interest from the people who could really help.
Be nice if we knew what caused this. I don't know what the three of us could have done to cause these problems. I have scoured google for answers and ways to repartition and tried so many things and I am giving up.
Hi guys,
So, I'll start by saying I haven't seen this problem before. And, if I had to venture a guess, I'd say your hardware is borked (not being able to format is a big clue).
But, there are some things to discuss and try before you use your devices as paperweights.
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
Third, I recommend avoiding touch recoveries. The best ones are still sketchy and it is very easy to do things accidentally. There is a reason that button CWM makes you scroll through 10 "no" before you get to "yes".
__________________
Please do the following:
1) Ensure that you are in fact running the correct version of fastboot with the correct drivers for your PC. Be 100% certain.
2) Enter fastboot mode and do "fastboot devices" (no quotes) and make sure your device is recognized.
3) If your device is properly recognized, try this:
a) "fastboot erase cache"
b) "fastboot erase userdata"
c) "fastboot erase boot"
d) "fastboot erase system"
e) "fastboot reboot"
After fastboot reboot does your device boot to OS, or stay on the boot logo? If your device stays on the boot logo, you wiped your OS (which is good).
Next install the most recent CWM button recovery.
If that works, flash a stable ROM. Nothing experimental - try a stock GB ROM (fruit cake, NottachTrix, etc.) or CM7 and see how things go.
There is some useful fastboot information available here.
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
upndwn4par said:
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
There is some useful fastboot information available here.
Click to expand...
Click to collapse
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
boonemeat said:
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
Click to expand...
Click to collapse
sjbayer3 said:
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
Click to expand...
Click to collapse
No. A newer version is fine, as long as you are using the correct drivers.
______________
What Recovery were you both using? I think one of you mentioned touch CWM.
______________
Have either of you tried Th3Bill's wiping tools? (I use them all the time)
Another way to install recovery would be via ROM Manager.
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!!!!
Hi,
my P760 is in a boot loop since yesterday. When it starts, the LG logo comes up and then it reboots again and again.
I tried the recovery option with the LG Tools, but after flashing the V20H-ROM, the bootloop is still there.
What can i do?
Thx
Mirko76
Today i tried fastboot and reflashed the bootloader:
Code:
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.210s
sending 'u-boot' (1024 KB)...
OKAY [ 0.530s]
writing 'u-boot'...
OKAY [ 0.210s]
finished. total time: 0.740s
Done
What does "partition does not exist" mean? is it dead?
Mirko76 said:
Hi,
my P760 is in a boot loop since yesterday. When it starts, the LG logo comes up and then it reboots again and again.
I tried the recovery option with the LG Tools, but after flashing the V20H-ROM, the bootloop is still there.
What can i do?
Thx
Mirko76
Click to expand...
Click to collapse
After flash stock rom, did you try to hard reset your phone? http://www.hard-reset.com/lg-optimus-l9-p760-hard-reset.html
Yes, but without success.
Mirko76 said:
Yes, but without success.
Click to expand...
Click to collapse
There're many boot loop thread in L9 forum, please search for it. You can try this one first http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
I tried a lot of possibilities to repair the bootloop, but nothing helped.
I flashed the ICS Bootloader and flashed an ICS Rom with the offline method, but after Flash the boot Loop is still there.
A hard reset doesnt help.
Mirko76 said:
I tried a lot of possibilities to repair the bootloop, but nothing helped.
I flashed the ICS Bootloader and flashed an ICS Rom with the offline method, but after Flash the boot Loop is still there.
A hard reset doesnt help.
Click to expand...
Click to collapse
Boot loop still there after flash kdz and hard reset! Strange. Flash kdz should restore factory rom and hard reset is remove all user data. What did you do before get that boot loop?
Did you try method in this thread http://forum.xda-developers.com/showthread.php?t=2411265
I did nothing before the bootloop. The battery was empty and after i plugged in the power supply, the phone was in the boot loop.
Mirko76 said:
Today i tried fastboot and reflashed the bootloader:
Code:
[B]
FAILED (remote: partition does not exist)[/B]
What does "partition does not exist" mean? is it dead?
Click to expand...
Click to collapse
It usually means hardware(NAND) failure
i got that same partition does not exist error when i was trying to flash the wrong xloader and uboot in fastboot. not saying you're flashing the wrong ones, but that maybe it has something to do with fastboot.. ?
Meda808 said:
i got that same partition does not exist error when i was trying to flash the wrong xloader and uboot in fastboot. not saying you're flashing the wrong ones, but that maybe it has something to do with fastboot.. ?
Click to expand...
Click to collapse
Could you have typed partition name incorrectly ? like "fastboot flash xloader..." instead of "fastboot flash x-loader..." ?
Lelus said:
Could you have typed partition name incorrectly ? like "fastboot flash xloader..." instead of "fastboot flash x-loader..." ?
Click to expand...
Click to collapse
i'm fairly certain i did 'x-loader' because i was copying the text in a batch file you wrote. hard to remember exactly. when it happened, reading about possible problem with the phone i got sad inside. if i ever need fastboot again i'll try it through vmware ubuntu install
Im using a fastboot script, so i dont think that the filenames are wrong.
Ok, i give up. I think the phone is dead.
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....