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!!!!
Related
This is not for my phone, but a friends...
Got an HTC EVO 3D with HBoot 1.5 that was unlocked with the HTC Unlocker Tool (from the HTC website). User had clockworkmod touch installed and tried to install ViperROM. Getting an error message (status 1) that looks like it is due to the ClockWorkMOD Touch version. He tried to downgrade the version to 5.0.2.0 and in doing so (did it from ROM Manager), he can no longer get in CWM. When booting to recovery via hboot, ROM Manager or Quick Boot, it shows the white HTC screen, then a plain black screen, then just reboots his phone back to the white HTC screen again.
Now he can't get into any CWM recovery. He's tried several different versions and can't get anything to work. I tried to flash the recovery 5.0.2.0 via fastboot and it says it was successful but it still won't boot into it.
Not sure where else to look for this one.
Just tried to flash via fastboot TWRP and no dice either. It said it was successful too.
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
metalfan78 said:
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
Click to expand...
Click to collapse
It is unchecked. I had todo that first. Fastboot sdes seem to be working.
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery y:\recovery-clockwork-5.0.2.0-shooter.img
sending 'recovery' (4726 KB)...
OKAY [ 1.187s]
writing 'recovery'...
OKAY [ 1.687s]
finished. total time: 2.875s
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery Y:\recovery-twrp-shooter-1.0.3.img
sending 'recovery' (5068 KB)...
OKAY [ 1.203s]
writing 'recovery'...
OKAY [ 1.703s]
finished. total time: 2.937s
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
dachef3184 said:
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I'm not sure that's correct.
He had CWM 5.0.2.0 that worked fine and he had the Touch CWM and it worked minus flashing ViperROM (possibly more, we did not try). He was able to launch CWM with a recovery reboot in ROM Manager, PowerButton and Quick Boot.
Holy crap this guy's phone sucks ass...
So, he flashed CWM back on 09/11/11 (which i think he was on hboot 1.4 or 1.3). He then flashed Synergy via CWM. He then tried to take an OTA update which failed but updated his hboot to 1.5. He hasn't flashed another ROM until just now.
He had the old CWM from before, and he is able to get the touch version (but it's usage is limited due to S-ON).
I'm just going to get him to flash a new ROM through fastboot and use 5.8.0.1 CWM Touch for nandroids, which still do work. I was able to get that CWM installed back on his device without a problem.
See the Guide/Flashing notes in my signature, i think it will help you out. Fyi, I've found only a few specific recovery versions work on my Hboot 1.50, Unlocked, S-On Evo3d.
I have hboot 1.5 and the only CWMs I've been able to get to boot properly are 4.0.1.4 and 5.8.0.1...the others I have tried always failed the same way yours did.
Please try the attached CWM or TWRP (both old versions/no touch screen) and tell if they work for you.....
OR
Try the touch CWM from here -> http://www.clockworkmod.com/rommanager
OR touch TWRP 2.0 from here -> http://teamw.in/project/twrp2
I've rooted and unlocked my MoPho as of now.
I've attempted to flash joker and romracer's recovery.
However, when I go to check to see how CWM is doing, I only get 4 options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Both of the videos I have watched show other options such as backup's and such. I'm not sure what I'm doing wrong, and any help would be appreciated!
Which clockwork are you using?
I have used this:
http://forum.xda-developers.com/showthread.php?t=1216143
and the
AIO root
The standard cwm (The one from market) gives me all the options.
However, when I try to flash jokers or romracers cwm recovery I just get the 4 basic options again.
Fastboot erase recovery and then use fasboot to install the new, one romracers or jokers your choice. If flashing CM9 id use Jokers.
That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.
cardinalsfre said:
That is the method I attempted to flash both of them with.
I still get the triangle with the arrow and the android by it that I have to press both the up and down volume buttons to show the recovery screen.
Click to expand...
Click to collapse
Thats the stock recovery.. You ARE unlocked correct? and you flashed it by putting phone into fastboot and with CMD pushing the new recovery?
Yes, I do believe I am unlocked.
Root check shows that I am rooted
Upon boot the phone says, "unlocked"
Yes, I am using the CMD prompt to attempt to flash, following qbking's video instructions.
Edit: Also, the CMD prompt says it has completed the recovery flash.
So you did all this below?
"moto-fastboot erase recovery
moto-fastboot flash recovery recoveryfilename.img"
and it came back saying
"sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]"
If so id to redownload the recovery.img and try again..
That worked, at first.
Upon first boot up I was greeted with the right recovery module.
When I went restarted to flash my ROM I was brought back to the original Android Recovery.
Edit: Should I flash on first boot up or should I wait until I can get the recovery to stick?
You have to go into the files and rename the stock recovery to ".bak" to make the new one stick. If I can find the link again, I will post it , or you can Google it? I think that's how I found it to begin with.
Thanks, that worked!
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
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....
Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.