So I have HTC One XL, S-OFF
yesterday i flashed various ROMs like5-7 different ROMs, i started noticing dropped network signals, so I did a factory reset from bootloader, which seems to have corrupted my internal sdcard, to repair it, i flashed stock recovery from androidruu dot com /?developer=Evita
file I downloaded is
OTA_EVITARE_UL_JB_45_TELUS_WWE_1.20.661.1-1.15.661.11_release_312229k92xgqqtl1xcfxt2.zip
extracted recovery.img from it, flashed this recovery from fastboot and then did a factory reset, after that flashed twrp 2.7.1 and booted into recovery then mounted my internal storage(which shows in my desktop as removable disk) then copied cm11 nightly then chose to install the zip but it fails saying
E:Mount: Unable to find partition for path '/sdcard'
Error flashing zip '/sdcard/cm-11-20140806-NIGHTLY-evita.zip'
Updating partition details...
can you please help me with this?
Thank you.
You didn't need to flash the stock recovery, you could have just used the advanced wipe option in TWRP to wipe the sd card, that usually fixes up any corruption.
Anyway, on to the major problem here. The OTA you downloaded isn't for this device (HTC One XL, codename Evita), it's for the HTC One X+ (codename Evitare), therefore the recovery you flashed isn't for this device, and therefore you've very possibly damaged your partition tables by doing the factory reset from it. It's very, VERY, important to pay attention to the details when messing around with your phone.
Now, how to fix this? It's still booting so that's a good sign. My advice is to try to run an RUU, you're s-off so any Evita RUU will be fine. The 3.18 at&t RUU is probably your best bet and you'll find it here:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
I'm not sure if this is going to work though because the RUU doesn't touch your internal storage partition. Maybe it'd be a good idea to perform a factory reset from the bootloader first, it'll corrupt your sd card but hopefully will repair its partition location at the same time. After you've done that go into TWRP and wipe your sd card, then try moving a ROM zip onto it again and flashing it. If that doesn't work then try the RUU.
Transmitted via Bacon
I cant believe I didnt saw that. sorry
Your 3.18 ruu link doesnt seem to work, please provide an alternative link.
what should i do now? run ruu or flash stock recovery then do a factory reset?
Here's an alternative link:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
Right now just try a factory reset from the bootloader, then enter TWRP and try wiping the sd card. See if that fixes it.
Transmitted via Bacon
no, wiping doesnt help
Were you able to access the sd to wipe it?
Transmitted via Bacon
timmaaa said:
Were you able to access the sd to wipe it?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes on mounting via twrp it shows up in my computer as a removable disk.
But you still can't flash a ROM?
Transmitted via Bacon
timmaaa said:
But you still can't flash a ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
noo, it returns same error...(....unable to find partition for path...)
Try the RUU now.
Transmitted via Bacon
timmaaa said:
Try the RUU now.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay i tried RUU, and the phone is working again with at&t logo appearing at first which it didnt when I first bought the phone.....but i guess the boot loader is locked again?
I cannot access bootloader by pressing volume down + power button, it just simply restart.
What should be my next step?
S1611 said:
Okay i tried RUU, and the phone is working again with at&t logo appearing at first which it didnt when I first bought the phone.....but i guess the boot loader is locked again?
I cannot access bootloader by pressing volume down + power button, it just simply restart.
What should be my next step?
Click to expand...
Click to collapse
Not being able to reach the bootloader is almost definitely a case of bad timing.
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Transmitted via Bacon
timmaaa said:
Not being able to reach the bootloader is almost definitely a case of bad timing.
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I got my bootloader screen
***UNLOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:12888
Flashed twrp 2.7.1.0, booted to recovery>factory reset>install>...error unable to mount...
S1611 said:
Okay I got my bootloader screen
***UNLOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:12888
Flashed twrp 2.7.1.0, booted to recovery>factory reset>install>...error unable to mount...
Click to expand...
Click to collapse
Hmm. I think that factory reset from the wrong recovery has assigned your internal storage the wrong partition location. The only thing I think will fix this now is a jtag repair.
Transmitted via Bacon
timmaaa said:
Hmm. I think that factory reset from the wrong recovery has assigned your internal storage the wrong partition location. The only thing I think will fix this now is a jtag repair.
Transmitted via Bacon
Click to expand...
Click to collapse
Any other alternative?
That that I can see. Your partitions are borked, a jtag repair forces the right partitions back into the device again.
Transmitted via Bacon
timmaaa said:
That that I can see. Your partitions are borked, a jtag repair forces the right partitions back into the device again.
Transmitted via Bacon
Click to expand...
Click to collapse
Good news :laugh::laugh::laugh: installed cwm recovery, and flashed as usual, and everything went fine. Running KarbonKat
S1611 said:
Good news :laugh::laugh::laugh: installed cwm recovery, and flashed as usual, and everything went fine. Running KarbonKat
Click to expand...
Click to collapse
Out of interest, what's the full filename of the TWRP recovery you were using?
Transmitted via Bacon
timmaaa said:
Out of interest, what's the full filename of the TWRP recovery you were using?
Transmitted via Bacon
Click to expand...
Click to collapse
openrecovery-twrp-2.7.1.0-evita
is it the wrong one?
S1611 said:
openrecovery-twrp-2.7.1.0-evita
is it the wrong one?
Click to expand...
Click to collapse
No that's the right one. Was just curious, it seems odd to me that CWM was able to flash the ROM but TWRP wasn't. I'd be interested to see if TWRP would work now after CWM has corrected your problem.
Transmitted via Bacon
Related
Try to unlock. Lots of things went wrong.
First the usb driver installed via installation of HTC Sync.
Open revolutionary and work on it, it stopped at "waiting for fastload".
So that I flushed a file - PG58IMG.zip, according to the noobproof post "method 2" here http://forum.xda-developers.com/showthread.php?t=1232107
It went wrong because I did not delete the file before rebooting. message: file error CRC.
While I use revolutionary to get into the bootloader again, I see this:
PYRAMID PVT SHIP S-OFF RL
Hboot - 1.17.0011
RADIO-10.11.9007.27_M3
eMMC-boot
Jun 2 2011,22:31:39
Then I can not use any key combination to enter bootloader.
If I use the revolutionary to get the the bootloader screen, it does not respond to the vol. keys and power key. Have to pull off the battery.
The phone can still boot normally.
Whay should I do to get the clockwork recovery flushed in?
Appreciated!
soma900 said:
Try to unlock. Lots of things went wrong.
First the usb driver installed via installation of HTC Sync.
Open revolutionary and work on it, it stopped at "waiting for fastload".
So that I flushed a file - PG58IMG.zip, according to the noobproof post "method 2" here http://forum.xda-developers.com/showthread.php?t=1232107
It went wrong because I did not delete the file before rebooting. message: file error CRC.
While I use revolutionary to get into the bootloader again, I see this:
PYRAMID PVT SHIP S-OFF RL
Hboot - 1.17.0011
RADIO-10.11.9007.27_M3
eMMC-boot
Jun 2 2011,22:31:39
Then I can not use any key combination to enter bootloader.
If I use the revolutionary to get the the bootloader screen, it does not respond to the vol. keys and power key. Have to pull off the battery.
The phone can still boot normally.
Whay should I do to get the clockwork recovery flushed in?
Appreciated!
Click to expand...
Click to collapse
First thing first, run RUU, then try revolutionary again, but READ THEIR HOW TO's!!!!! Again, read their HOW TO's!!!!!
If you have no RUU available you'll have to mess about with ADB, which is not that easy for a newbee.
Google on how to install ADB and stuff, once it's running and working properly, you have to type
adb reboot bootloader
fastboot flash recovery recovery_name.img
fastboot reboot-bootloader
But if your buttons still don't work, you won't be able to get into recovery.
Anyway, there are a lot of things you can do, i can sit here all night trying to write up different scenarios, but best thing for you to do is to start from scratch (RUU->REVO etc) AND READ HOW TO and don't rush when you do it.
P.S. Have you tried booting into bootloader by holding -vol button while pressing power button (after battery pull, as if you just shut it down, you might still have fast boot enabled)? Should really start from that.
tinky1 said:
P.S. Have you tried booting into bootloader by holding -vol button while pressing power button (after battery pull, as if you just shut it down, you might still have fast boot enabled)? Should really start from that.
Click to expand...
Click to collapse
Already tried many times. Either vol-down + power, or vol-up + power, the phone will start to sense. I can get into bootloader screen via revolutionary, but it does respond to menu change by holding the vol-up, or down and run by power button.
Unlocking the first time. Also new to android. used to be stick with win for years. Thanks Tinky1! I will try revolutionary again. Please stay with me.
New developemnt.
Try the revolutionary again. This time I put the cwm rocovery tools 5010 as a zip on the card beforehand. This time the Rev screen still shows "Communication with the phone interrupted unexpectedlly ......". But on the phone it now shows "Hboot - 1.17.1111". Then I unplug the USB, boot in rocovery. This time it responsed. Wait untill it says update completed, then restart phone into sense home screen.
I guess this time it is alright.
Yes. Now I can goto blue CWM recovery menu. The next figure out which rom to flush my phone. Thanks, Tinky1!
soma900 said:
Yes. Now I can goto blue CWM recovery menu. The next figure out which rom to flush my phone. Thanks, Tinky1!
Click to expand...
Click to collapse
You should change title since u found solution
Sent by my feau gee
Im currently running Cm 10.1 jellybean and my data connection goes in and out and i would just like to go back to stock
im S-on
Hboot 2.15
S4
T-mobile
Yaphet Kotto said:
Im currently running Cm 10.1 jellybean and my data connection goes in and out and i would just like to go back to stock
im S-on
Hboot 2.15
S4
T-mobile
Click to expand...
Click to collapse
1. Go to recovery [Press power button and Vol-down button until your phone switches off, then release the power button and keep holding the vol down button, it will take you to bootloader, release the vol button now and select recovery - (Volume buttons to move and power button to select)].
2. Then select backup/restore option, then select "restore" option. You will see the nandroid backup you have made, and then select it to restore.
3. After that, do not reboot your phone but reboot it into Bootloader (see step 1)
4. Plug in your phone to PC, you should see "fastboot USB"
Now you have to flash the boot.img (to make your phone boot past the htc splash screen), which will be in your nandroid backup folder.
Keep the boot.img in your adb/fastboot directory and in command prompt type the following command WITHOUT QUOTES
"fastboot flash boot boot.img"
Then reboot your phone.
OR
If you have trouble using the ADB fastboot or command prompt, you can flash the boot.img using "FlashImageGUI.apk" (download the release free version) and can flash the "boot.img" BEFORE restoring your nandroid backup. After flashing boot.img, you will see the option (Reboot to recovery) and then follow step 2 and restart your phone.
moses.finney said:
1. Go to recovery [Press power button and Vol-down button until your phone switches off, then release the power button and keep holding the vol down button, it will take you to bootloader, release the vol button now and select recovery - (Volume buttons to move and power button to select)].
2. Then select backup/restore option, then select "restore" option. You will see the nandroid backup you have made, and then select it to restore.
QUOTE]
I actually didn't backup my stock rom so can I download a stock.zip and flash it that way?
Click to expand...
Click to collapse
Yaphet Kotto said:
moses.finney said:
1. Go to recovery [Press power button and Vol-down button until your phone switches off, then release the power button and keep holding the vol down button, it will take you to bootloader, release the vol button now and select recovery - (Volume buttons to move and power button to select)].
2. Then select backup/restore option, then select "restore" option. You will see the nandroid backup you have made, and then select it to restore.
QUOTE]
I actually didn't backup my stock rom so can I download a stock.zip and flash it that way?
Click to expand...
Click to collapse
Yes, you can download a stock zip and flash it with the same process. But make sure that stock zip suits your version of phone, as there are versions like S3, S4, T-mobile etc.
Click to expand...
Click to collapse
moses.finney said:
Yaphet Kotto said:
Yes, you can download a stock zip and flash it with the same process. But make sure that stock zip suits your version of phone, as there are versions like S3, S4, T-mobile etc.
Click to expand...
Click to collapse
I also want to go back to stock. I have the htc one s "ville" US T-Mobile varient, but I don't which ruu to download. Right now I'm trying to fully unroot and ruu back stock, so bootloader is relocked and everything.
Click to expand...
Click to collapse
arDroid.99 said:
moses.finney said:
I also want to go back to stock. I have the htc one s "ville" US T-Mobile varient, but I don't which ruu to download. Right now I'm trying to fully unroot and ruu back stock, so bootloader is relocked and everything.
Click to expand...
Click to collapse
Look at this page
It might help you. If the download link is not working, you can ask the member who started the OP.
Click to expand...
Click to collapse
moses.finney said:
arDroid.99 said:
Look at this page
It might help you. If the download link is not working, you can ask the member who started the OP.
Click to expand...
Click to collapse
Thanks, but how do I use ruu?
Click to expand...
Click to collapse
arDroid.99 said:
arDroid.99 said:
Thanks, but how do I use ruu?
Click to expand...
Click to collapse
Flash stock recovery first in FASTBOOT USB using the command
Code:
fastboot flash recovery ville_recovery_signed.img
The second download link is the stock recovery image i guess.
Then, you will have to relock the bootloader using the command
Code:
fastboot oem lock
While in the FASTBOOT USB , run the RUU from Windows and follow the wizard. Once the installation process is complete, you will have to unlock your bootloader again using the token you have from HTCdev first time. Flash CWM recovery, and root again.
Don't forget to flash the stock recovery first, or you will get an error.
Click to expand...
Click to collapse
Hello,
I've installed CM10.2 and want to go back to stock rom! I tried all steps here, but it doesn't work Is there any other way to go back to stock rom?
With the RUU I get the message "Hboot Version is older". Pls help
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
cyverboy2 said:
Hello,
I've installed CM10.2 and want to go back to stock rom! I tried all steps here, but it doesn't work Is there any other way to go back to stock rom?
With the RUU I get the message "Hboot Version is older". Pls help
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
Click to expand...
Click to collapse
Well if your RUU.exe is unable to run because your Hboot is newer then you could try this stock rom: for the VilleC2
http://forum.xda-developers.com/showthread.php?t=2374476
tivofool said:
Well if your RUU.exe is unable to run because your Hboot is newer then you could try this stock rom: for the VilleC2
http://forum.xda-developers.com/showthread.php?t=2374476
Click to expand...
Click to collapse
I need to send it back to HTC because my vibration alarm is not working, so I have to go back to stock! Any other way?
cyverboy2 said:
I need to send it back to HTC because my vibration alarm is not working, so I have to go back to stock! Any other way?
Click to expand...
Click to collapse
Sending it back for vibration alarm? You sure it is a hardware problem?
I would first try that stock rom and see if it is fixed. If not, you will most likely need to s-off to get everything back to stock.
(or find a stock nandroid and restore that and fastboot flash the boot.img, then flash stock recovery, relock bootloader and factory reset) close enough.
Hi,
whenever I put my OPO into fastboot mode all I see is a dark grey CM cat with "Fastboot mode" written underneath. All fastboot commands work as expected but it would be nice to be able to see some more info (e.g. bootloader version and radio version, amongst others) I am coming from a Nexus 4 and 7 and an HTC device before that. All have/had this info on the bootloader screen.
And while we're at it: is there a way to boot directly into recovery from the bootloader screen? fastboot only knows a full reboot or a reboot-bootloader.
Cheers
Michael
The fastboot mode on this device isn't like the bootloader you'd find on a HTC or a Nexus. It might be nice to have that information, but it simply isn't the case with this phone. Have you tried the recovery button combo (power + volume down) to get to recovery?
Transmitted via Bacon
timmaaa said:
Have you tried the recovery button combo (power + volume down) to get to recovery?
Click to expand...
Click to collapse
I know this one. However, actually I was looking for a way to get into recovery directly from the bootloader without rebooting or powering down beforehand. Something like "press volume down twice then power to get directly into recovery". Will check myself and report back here if I find something.
Thanks again.
finistere said:
I know this one. However, actually I was looking for a way to get into recovery directly from the bootloader without rebooting or powering down beforehand. Something like "press volume down twice then power to get directly into recovery". Will check myself and report back here if I find something.
Thanks again.
Click to expand...
Click to collapse
Don't waste your time, such an option doesn't exist.
Transmitted via Bacon
I had TWRP custom recovery installed, but I wanted to run an OTA update so I tried to flash back to stock recovery. My phone is now stuck in a reboot loop. It sits at a black screen with a small picture of an M8 and a red triangle and exclamation mark over it, then eventually it reboots. It boots to the white screen with the green "htc" logo, then goes back to the same black screen. I've tried holding down the power button, holding down Vol down+Power, holding down Vol up+Power, and holding down all three, but the reboot loop continues. Fastboot does not see my phone at any stage.
Here are the steps that I followed to arrive at where I am now:
1. Booted to Fastboot
2. Connected my phone to my PC
3. Opened a CMD prompt and accessed the fastboot directory
4. Ran this command: Fastboot oem rebootRUU
5. Ran this command: fastboot devices
6. Ensured that my phone was listed
7. Ran this command: fastboot flash recovery stock-recovery-4.4.3.img
8. Received a message stating that it was successful
9. Opened HBOOT on my phone
10. Opened Recovery on my phone
11. Phone went to a black screen with a small picture of a phone and a red triangle and exclamation mark
12. Phone stays there for a little while, then reboots to this screen, then the cycle starts over again
I did some searching but I couldn't find anything that helped. Anyone have any ideas?
Sorry, I mistakenly posted this in the wrong forum. Mods, could you please move this to Help & Troubleshooting?
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
craichead said:
UPDATE: I was able to get into fastboot by quickly holding down Vol Down + Power in between boot cycles, and fastboot is seeing my device on my PC. The problem now is that I don't know what to do from here.
Click to expand...
Click to collapse
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
ΠΣΘ said:
What you are seeing is stock recovery. That is normal so relax.
What it sounds to me that you are wanting to do, is put your phone into a stock enough state in order to take any upcoming OTA correct?
I suggest at this point, that you take the latest available RUU (which has the latest OTA firmware included) which is also pre-rooted.
You will need to be able to get into Hboot however and you can do this by doing the following:
Hold Power+Volume up until the screen shuts off and goes black, then IMMEDIATELY hold power+volume down until you boot into hboot.
Once in hboot, you can always fastboot flash back TWRP to get your custom recovery back and flash custom roms.
I would do that first if there are things on your internal memory that you wish to save and off-load to your pc prior to taking the RUU.
If there is nothing you wish to save and you're ready to return to stock (but rooted so you can get back into the custom game later if you like), then follow the instructions outlined in the OP of this thread (which will provide a link for you to download the RUU needed): http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
If S=ON, select the S=ON link.
If S=OFF, select the S=OFF link.
Neo
Forum Moderator
Click to expand...
Click to collapse
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
craichead said:
I actually don't think that it's in stock recovery. It still won't power on and is stuck in a reboot loop unless I hold Vol Down+Power during the reboot.
Click to expand...
Click to collapse
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
ΠΣΘ said:
Hold down Volume UP+Power for about 10 seconds until the screen goes black and then immediately hold Volume Down+Power until you get into hboot.
Click to expand...
Click to collapse
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
craichead said:
I can get into HBOOT just fine, but no further. It's almost as if recovery isn't even installed.
Click to expand...
Click to collapse
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
ΠΣΘ said:
You DO NOT NEED to flash stock recovery if you are wanting to return back to stock.
If there is nothing on your internal memory that you are wanting to save, then follow the instructions for flashing the RUU in hboot via rename and sdcard. I gave you the link you needed to follow which outlines precise directions to get you completely functional again in the phone state you desire.
Click to expand...
Click to collapse
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
craichead said:
Everything I've read says that you do need to flash stock recovery in order to receive OTA updates, which is what I'm trying to do. I'm not trying to flash a zip.
Click to expand...
Click to collapse
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Flashing the RUU will flash the stock recovery.
Sent from my HTC6535LVW using Tapatalk
ΠΣΘ said:
You need to be on stock firmware in order to take a OTA. That means stock firmware with FOTA enabled, and stock recovery.
Flashing a RUU returns you to a stock state of re-locked hboot, stock recovery, and stock rom with FOTA enabled. I can't help you any more if you don't follow the directions sir.
Flash the RUU and profit.
Good luck,
Neo
Click to expand...
Click to collapse
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
craichead said:
I appreciate your help, but this isn't about me not following directions. I'm trying to figure out why my stock recovery doesn't seem to be flashing properly and, no disrespect intended, but you haven't addressed that issue directly.
Click to expand...
Click to collapse
None taken. I have not addressed the failed recovery flash because it could be a number of different reasons. I don't dwell on why things don't/didn't work.. I focus on the primary objective. Your primary objective was outlined in the OP of this thread and is as follows:
craichead said:
I wanted to run an OTA update
Click to expand...
Click to collapse
If the rom currently on your phone is in a completely stock state and simply rooted with no system files deleted or modified, then what you attempted to do with simply flashing a stock recovery would have been the minimally required thing to do.
If however you've deleted system files or flashed to a custom rom, then you will need to return your device to a stock rom, with fota enabled, and stock recovery flashed. The easiest method to achieve this directive is to flash a RUU, which contains all of the above requirements for being in a state to receive any OTA on top of updating all of your firmware to the latest OTA that we've received to date.
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
craichead said:
I do see your point, and loading the RUU might well work. But I would prefer to be able to back up my apps beforehand and I can't do that if I can't boot up. I did successfully re-flash TWRP recovery, but for some reason it still won't boot up; it's stuck in the reboot loop that I described (though I am still able to get into HBOOT).
Click to expand...
Click to collapse
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
ΠΣΘ said:
Dirty flash (without wiping) the rom you are currently on. If S=ON, fastboot flash the included boot.img with it as well.
Click to expand...
Click to collapse
Does that mean just restoring my backup in TWRP? I am S-OFF.
craichead said:
Does that mean just restoring my backup in TWRP? I am S-OFF.
Click to expand...
Click to collapse
That should work also, yes.
ΠΣΘ said:
That should work also, yes.
Click to expand...
Click to collapse
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
craichead said:
That worked! Thank you. I have all of my apps and they're all organized the way that I had them. I'm guessing the next thing I need to do is do a back-up, then flash the RUU, then the OTA should work?
Click to expand...
Click to collapse
Yes. However, if you flash the latest RUU, you won't receive any OTA because the latest RUU contains all the firmware from our most recent OTA lol. You will be in a state though to receive any future OTAs should they come.
Make sure to back up your internal memory to either your sd card or your computer as the internal memory gets wiped in a RUU.
So I downloaded the RUU, but I can't seem to be able to copy the file to the external SD card as instructed. I go into ES File Explorer and access Device\storage\ext_sd and try to paste it there, but it says "not enough space". Which is weird, because it says that the directory is empty (and hidden files are enabled).
I believe I've bricked my OPO. I was trying to flash OxygenOS today and it wasn't flashing completely right. I decided to not try anymore and flash back to 05Q. However, in doing that I bricked my phone. Volume- and power doesn't bring me to recovery, I can't access bootloader. However when I press volume- and power it still sounds the connection and I can see it in my device managers, I just can't do anything. When I try to do anything through ADB it says no fastboot devices found. CUrrently, my phone doesn't have boot.img, recovery.img, and system.img. I do have a latest backup of my 05Q from this morning before I did all of this.
Any help would be great. Thanks!
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Try one plus one recovery toolkit 1.0 it will slove ur problem same think happens to me it will help me
timmaaa said:
Try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Click to expand...
Click to collapse
Definitely works. Just did the same after I tried to downgrade from OxygenOS and bricked my device.