Related
Not even sure where to start. I've had my One S (TMO) for about 2 weeks now. I immediately followed all the guides to unlock my bootloader, install custom recovery and install custom ROMs. Was running Viper OneS for a while and then switched over to TrickDroid (both 7.0.0 TMOUS and 8.1.0). All of the ROMs seemed to give me some odd issues.
With Viper OneS (after patching my services.jar) I was able to install SManager and run the V6 supercharger script, but after reboot, I was no longer able to get into the ringtone and notification sounds options on the device. When I went to either screen they were just blank and I couldnt choose music from any location on the phone.
With TrickDroid 7.0.0 TMOUS, I was able to patch services.jar and run the supercharger script without any issues at all. However, after a few days of usage, I noticed that calls were no longer forwarding the voicemail number I setup using an MMI code. From there I went to TrickDroid 8.1.0 but even after patching my services.jar, my supercharger settings would not stick after reboot.
Here's where I think something went wrong. I wanted to go back to stock but rooted. Since there were no 2.35 RUUs available for download anywhere, I decided I would download the 1.84 RUU and then get the OTA update. I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems. Unlocked the bootloader and installed TRWP 2.2.2 so that I could flash supersu and root the phone and noticed that the phone was not acting right. From TWRP, its almost impossible to get the phone to reboot. When I choose to reboot, the screen goes blank, flashes once or twice and the notification light keeps turning from orange to green and then back again. I have to hold power down for about 10 seconds, then hold volume and press power to get into bootloader just to turn the phone on.
Decided to try going back to a custom ROM and noticed something else that is strange. I wanted to flash TrickDroid 7.0.0. and during the flashing, it hung on flashing the kernel for like 5 minutes when it usually takes just a second. I then flashed the fusion v2.1 kernel and it hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds. After the flashing was done, I booted up the ROM and when I went into settings, the new kernel was not installed. I flashed it again in recovery and booted back to the ROM and still the stock kernel was showing.
Could I have somehow really screwed up my phone throughout this whole process? Is something corrupted on the NAND that is causing issues with rebooting recovery and flashing things?
[email protected] said:
I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems.
hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds.
Click to expand...
Click to collapse
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
dc211 said:
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
Click to expand...
Click to collapse
Thanks for the info! Glad to know I didnt mess anything up .
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
EDIT: Wow.... i feel really dumb now. All posts I found while searching included the extra "recovery" in the commany. I just ran fastboot boot recovery.img and all is well.
[email protected] said:
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
Click to expand...
Click to collapse
.
I doubt that the actual recovery img is named recovery.img. If I am correct that is your problem. You would be trying to boot a recovery img that doesn't exist. It should be:
fastboot boot recovery [name of recovery file].img
Example:
fastboot boot recovery cwm_5.8.3.1_ville_recovery.img or something to that effect (not sure what the actually file name is)
if you are not sure on exact name as behold mentioned, just right click on the file (.img) wherever you have it on pc, check properties, and it will tell you exact name. at that point i just copy and paste it to command window--
hello
in the process of upgrading hboot (now on 2.40)
phone is not booting beyond bootloader
i have applied (pretty sure i have) supercid, the old unlock bin file i had is no longer working.
i can get into twrp, but after flashing rom, phone will not restart
any tips would be appreciated!
oops, didnt realise i needed to flash the boot.img on 2.40 hboots... all good.
Hey, First post and it going to be about whether my phone is bricked for good or not. =/ I'd really appreciate some help as I've clearly not researched enough into this.
-My Rogers HTC One X had previously been rooted and unlocked to hboot 1.09 with cyanogenmod.
-I wanted to install Android Revolution HD, so i figure I needed an hboot update. I went ahead and flashed the phone with the 'firmware.zip' in 'OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip' (HUGE MISTAKE)
-After flashing, I tried to install Android Revolution HD but it had crashed mid way.
-Im able to access hboot and Im also able to go into fastboot and recovery (recovery-clockwork-6.0.2.8-evita).
-Rebooting the phone results in a blank screen after the HTC loading screen. So no adb.
My hboot shows this:
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I've tried locking it, flashing it with PJ83IMG.zip but it says: 'FAILED (remote: 44 hboot version check fail)'.
I've tried running 'RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe' but it gets half way and has Error 155.
Can anyone recommend a rom that will work in this configuration?
Any chance that I can still get S-off on the phone?
Any way to recover the phone at all? Just to be clear, I've flashed my Rogers phone with a Rogers OTA.
Thanks!
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Nevermind
Sent from my One XL using XDA Premium
Also that Rom is for the international HTC one x if the install hadn't crashed it would have bricked your phone
Sent from my HTC One X using Tapatalk 2
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
certitude said:
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
Click to expand...
Click to collapse
If you are going to s off, no need to really downgrade. This because you are turning security checks off. So it actually makes things a bit easier, and decreases the chances of bricking. I'm s off and on hboot 1.14 and was able to flash plenty of roms without a computer.
Sent from my Carbon-ize Evita using xda-developers app
You're not limited. You just need to fastboot flash boot boot.img any time you flash a ROM. If you're not a flashaholic like most of us, it's no big deal.
I wouldn't RUU with S-ON though, even though you didn't supercid, I bricked without supercid running an RUU after rooting.
So, if you don't plan to RUU you don't need to S-OFF either.
If you do intend to S-OFF, since you didn't need to supercid to unlock your bootloader, you would need to hex edit your CID to 11111111 if you wanted to S-OFF.
If you have any other questions, don't hesitate to ask but I suggest reading the stickies in all the sections. Good Luck
Thanks for the info everyone. I'll be keeping that in mind.
exad said:
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Click to expand...
Click to collapse
I got a Telus HTC one x yesterday. Spent all day reading about rooting etc and finally went ahead and did it. The unlocking part went without a hitch. I then went to install the clockwork recovery and I think I used an outdated one, because after I did it, it wouldn't boot into recovery. I could get into the bootloader, but checking anything else it wouldn't do anything. At that time I was still able to boot up my phone as normal. I then saw an updated clockwork recovery and tried that one, and it still wouldn't respond when I clicked on recovery. Now I can't do anything except get into the bootloader. My screen says the exact same thing as the original poster in terms of
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I'm so upset right now. I read your instructions on what you suggested to the OP but theirs was Rogers and mines Telus, and I never did have a custom ROM on there, and I don't have a clear cache option, just a 'clear storage'
Even selecting the 'reset phone' doesn't work. I'm ready to cry lol. I don't want to touch anything without guidance so I don't screw it up even further. I know this is the rogers forum but it's what came up when doing a google search.
Please help me. Please tell me this can be fixed. :crying:
Don't use CWM, use TWRP instead. Find version 2.3.3.1 at goo.im (just Google TWRP 2.3.3.1 evita download). Check the md5 of the download is correct. I'm assuming you have fastboot on your pc.
Put the TWRP recovery.img in your fastboot folder
Boot phone into bootloader, wait for it to say "fastboot usb" on the screen of your phone
Open a command prompt in that folder on your pc
Type in the following command:
fastboot flash recovery openrecovery-TWRP-2.3.3.1-evita.img (whatever the name of the recovery image is, I think that's right)
It will now write the recovery to your phone, wait for it to finish, it should only take a few seconds
Now type the following command in:
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to disconnect your phone and flash superuser.zip in your new recovery and have root access.
Sent from my HTC One XL using xda premium
omg!!!!! TY TY TY TY TY!!!!!!!!
It flashed into recovery!!!!!
I can't find where my superuser went...is there a way I can get it onto my phone? At this point I'm so nervous about screwing anything up that I'm afraid to play (which is rare for me as I'm normally quite good at all this stuff)
Do I really need the superuser? I'm planning on putting the ViperXL 3.2.7 rom on my phone. Can I just go straight to installing the rom?
I know where I went wrong now though. I used the international root instructions and not the AT&T ones as I assumed since I was Telus instead of Rogers or AT&T that that was the one I needed. Ugh! I feel like such an idiot!! I had android for quite a while then went to iphone for a little while (mistake) and had gotten so good at doing everything with those and forgot most of the steps involved with rooting android and the terminology. I'm happy to be back home with android!
You can just go ahead and flash ViperXL, that is pre-rooted so you'll be good to go. I just assumed you had a ROM running, so flashing the superuser zip would have just given that ROM root access.
Now, just make sure you stay here in the One XL (AT&T) forum. Make sure you only flash ROMs from here, because flashing one of the International ROMs can brick your phone, and we don't want that.
Sent from my HTC One XL using xda premium
I will be staying here!! lol
Just to be sure I have this correct...
I downloaded Viper and the boot img.
I'm going to go back to my cmd prompts, install the boot img
I'm getting hung up with understanding how to place the zip on my phone storage...My computer isn't showing it as being a separate drive.
I keep getting 'failed' errors with everything in TWRP. If I try to mount as USB storage, my computer says it needs to be formatted...
When I try to do anything else it shows up with failed.
Ok here's what you'll need to do:
Boot your phone into the bootloader (hold power and volume down key together, release power after a second but keep holding volume down until you're in bootloader)
Select recovery
Once recovery boots up, connect to pc with usb cable, select mount in recovery menu, then select mount storage
Your phone should now show up on your pc as a drive, copy the entire ROM zip to your phone
Once it's copied, do eject and safely remove the drive from your pc, and hit unmount on your phone screen
Hit the home button (little house on bottom left) in recovery
From main recovery select wipe, once in wipe menu you must wipe cache, dalvik cache, factory reset, and system
Once you've wiped all those, hit the home button again
Select install from the main recovery menu, then find the ROM you previously copied to your sd card and select it, then swipe to install, let the install finish (please note: if you're installing viper, it will have a few options to select during the install, select the ones you want. But right at the end of the install process there will be a checkbox for "reboot device now" and it will be checked, make sure you uncheck that before you hit finish/done)
Now you'll see two options, wipe cache/dalvik is one, do that, once that's done hit the home button again
From the main menu, hit reboot, and then bootloader, your phone will now boot back into the bootloader and fastboot usb should show up in red text on your screen if your usb cable is still connected
Now back to the pc, Copy the boot.img from the ROM zip and place it in your fastboot folder
Make sure you're connected with usb and fastboot usb is showing on your phone screen
Open a command prompt in your fastboot folder on pc and type in:
fastboot devices
You should see a device number return in the command prompt, if that shows up you're connected properly, so now type in the following command:
fastboot flash boot boot.img
This will flash the boot.img to your phone, let it finish
Once that's done you can reboot and you should be able to reboot into your new ROM
Sent from my Evita
It's not mounting...just keep getting a message from my computer that the drive needs to be formatted before I can use it...
btw, ty for all your help on this you've been amazingly helpful!
You may have corrupted your sd card. You'll have to format it, which means you'll lose all your data off it unfortunately. Do that first and then start again.
Sent from my Evita
It worked!!!!!! It booted up into Viper!!!!! TY a million times over!!!!!!!!!!
Awesome, so glad to see you got it going :thumbup:
And no problem at all, my pleasure, this is what XDA is all about.
Sent from my Evita
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
deepak_raja20 said:
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
Click to expand...
Click to collapse
Well i got S-OFF with Rumrummer but i got it till my 7th try. you should keep trying with it
Stuck in sending recovery/sending zip flash
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
deepak_raja20 said:
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
Click to expand...
Click to collapse
I suggest you get the OTG USB cable. Load the ROM on a Flash USB and then use TWRP to install the ROM (Remember to mount the OTG in TWRP) Check Amazon, it only cost less than $3. I've never push the ROM to the phone. Saves a lot of time when you have multiple phones.
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).