Related
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
valery.m said:
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
Click to expand...
Click to collapse
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
valery.m said:
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
Click to expand...
Click to collapse
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
nkk71 said:
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
Click to expand...
Click to collapse
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Guich said:
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Click to expand...
Click to collapse
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
nkk71 said:
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
Click to expand...
Click to collapse
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Click to expand...
Click to collapse
You're right :good: With s-off, so no problems locking/unlocking etc
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
valery.m said:
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
Click to expand...
Click to collapse
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Click to expand...
Click to collapse
I want phone to do it itself It can "see" the OTA update - so let it to flash! :laugh:
nkk71 said:
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Click to expand...
Click to collapse
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
valery.m said:
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
Click to expand...
Click to collapse
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
nkk71 said:
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
Click to expand...
Click to collapse
Same version there
ROM is stock, it was updated via OTAs from 4.1.2 to 4.2.2. All was fine.
Only my customization is rooting, s-off and unlocking bootloader.
valery.m said:
Same version there
Click to expand...
Click to collapse
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
nkk71 said:
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
Click to expand...
Click to collapse
Thanks for the idea, i will try it!
valery.m said:
Thanks for the idea, i will try it!
Click to expand...
Click to collapse
Good luck, and if you do (and wanna help the rest of the community) can you try with both ROOT and unlocked bootloader first, and see if it works.
I know it's a bit of a hassle but at least you would be able to confirm if ROOT or unlocked bootloader are interfering with the update
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
steelmaggot said:
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Can you describe the whole procedure?
Sorry guys, i'm not so patient - so flashed new firmware from OTA's zip archive, flashed TWRP and then flashed ARHD. I'm happy now
Hi.
I should start by saying that I am completely new to rooting phones. I think it's fair to say that I am in over my head!
I am attempting to return my HTC One M7 back to stock. I have relocked to bootloader but am unable to find a RRU that is compatible with my device. I basically want my phone as it was (able to receive official OTA's etc). My phone is S-on and hasnt been S-off. I'm not confident enough to go S-off.
My phones details are shown in the attached photo. My CID is ORANG001 (UK EE).
I have been through the extensive list but none are compatible with my device.
Any assistance offered would be appreciated. Remember - speak slowly!
Thanks.
IchiKiriyama said:
Hi.
I should start by saying that I am completely new to rooting phones. I think it's fair to say that I am in over my head!
I am attempting to return my HTC One M7 back to stock. I have relocked to bootloader but am unable to find a RRU that is compatible with my device. I basically want my phone as it was (able to receive official OTA's etc). My phone is S-on and hasnt been S-off. I'm not confident enough to go S-off.
My phones details are shown in the attached photo. My CID is ORANG001 (UK EE).
I have been through the extensive list but none are compatible with my device.
Any assistance offered would be appreciated. Remember - speak slowly!
Thanks.
Click to expand...
Click to collapse
Restore you stock backup .. their is no files available for your phone
Thanks.
How would I go about that?
IchiKiriyama said:
Thanks.
How would I go about that?
Click to expand...
Click to collapse
do you have custom recovery ?
IchiKiriyama said:
Thanks.
How would I go about that?
Click to expand...
Click to collapse
just on a side note, please tell us you DIDNT re-lock your bootloader with a cutom recovery on your phone like TWRP or CWM ?
sorry to butt in @clsA just had to ask as I wouldnt know what to do for him if there is no files availble.
I had attempted to install a custom rom but the installation failed and it factory reset my phone. Basically, I appear to be using my stock RUU but ota is appears to be disabled. I attempted to install this rom, followed these instructions: http://forum.xda-developers.com/showthread.php?t=2189373
IchiKiriyama said:
I had attempted to install a custom rom but the installation failed and it factory reset my phone. Basically, I appear to be using my stock RUU but ota is appears to be disabled. I attempted to install this rom, followed these instructions: http://forum.xda-developers.com/showthread.php?t=2189373
Click to expand...
Click to collapse
Ok that's fine
you need to unlock the bootloader now at htcdev.com so you can flash the correct recovery to you phone
download TWRP 2.8.5.0 here > http://techerrata.com/browse/twrp2/m7
flash it
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and copy your rom to your phone again and install it again
no need to wipe again / theirs no RUU for your phone so no need to relock the bootloader any more
Very helpful. Thanks.
I'm sorry to cause further frustration, but could you give me simpler instructions? I don't want to make my situation any worse!
As I said above, I'm in way over my head.
IchiKiriyama said:
Very helpful. Thanks.
I'm sorry to cause further frustration, but could you give me simpler instructions? I don't want to make my situation any worse!
As I said above, I'm in way over my head.
Click to expand...
Click to collapse
Humm that's as simple as it gets
go to http://www.htcdev.com/bootloader
follow the instructions to unlock the bootloader
when it's done download TWRP 2.8.5.0 and Flash it same as you did the unlock token above, in a command prompt from the folder with fastboot in it.
when you get to the TWRP recovery screen copy your rom to the phones storage and then click install it in TWRP
choose your file you just copied and let it install
the first reboot to lollipop will take a long time ...be patient
actually your not on 7.x firmware .. you need to flash an older rom
Use this one >> https://www.androidfilehost.com/?w=files&flid=22071
it matches your firmware better
Thanks. And that'll return my phone to stock?
I have been running this rom for quite some time and I wanted to know the procedures while being s on to upgrade the entire phone. I'm also enclosing a screenshot of my current firmware and ROM. Any help would be greatly appreciated I haven't done this since I first got my m8
Download the most recent RUU from the thread linked below to your computer:
http://forum.xda-developers.com/showthread.php?t=2729173
Make sure your phone has a full charge. Reboot your device to the bootloader and connect your phone and computer via USB cable. Select the fastboot option from the menu and you should show that you're connected via fastboot USB mode. Open up a command window with ADB and type the command "fastboot oem lock". Press enter. This command will re-lock your boot loader. Now, double-click the RUU file you downloaded to start the installer. Be patient, as it may take a few minutes for the installer to start. Once it starts, follow the prompts on your computer screen. Once the RUU completes you can disconnect your phone from your computer and reboot your phone. The RUU will wipe the internal storage on your phone, so make a back-up and store it on your computer or your external SD card, if applicable.
Can i unlock the bootloader again after doing all this by typing fastboot oem unlock in adb?
I just wanna make sure I update everything correctly and get set up for a new Rom. I'm not getting all my calls or texts. So I am guessing the radio is too outdated
Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once
honorlost84 said:
Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once
Click to expand...
Click to collapse
RUU
Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again
honorlost84 said:
Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again
Click to expand...
Click to collapse
The stock recovery will be installed. Additionally, you'll need to use HTC Dev to unlock your phone again. That's the best way to update being S-on.
So there's no way to just update the firmware and radio without having to go through the rest of that?
Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu
honorlost84 said:
So there's no way to just update the firmware and radio without having to go through the rest of that?
Click to expand...
Click to collapse
Without being S-off, no.
honorlost84 said:
Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu
Click to expand...
Click to collapse
Firewater has been discontinued. You have to use the Sunshine exploit for S-off.
Got a link?
honorlost84 said:
Got a link?
Click to expand...
Click to collapse
Sunshine
Sloth you deserve some Rocky road buddy
And this is what I get. I suppose nothing is simple. I got no clue what is wrong.
Kernel info
Flash a stock rooted ROM from the RUU thread I mentioned previously, then try it again.
I locked boot. Ran a ruu from boot and destroyed my os and it took me all night to recover. Can you please show me how to restore to stock? I'm kinda over it
Now that you've run the RUU, go ahead and run the Sunshine exploit. Afterwards you can go about installing recovery and flashing a new ROM, if you'd like.
Not paying 25 bucks. I'm just wanting stock. My phone got too close to getting the hammer. I'm just gonna go stock. Don't know how
Huge amount of frustration with trying to deal with my phone
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
F0rZ3r0 said:
I soft bricked my HTC One M8 HK not too long ago, and had left it sitting in the dust for a while as I had no options of fixing it because I wiped the memory on accident (how I did, I don't know. Guess I'm dumb. That's not the point though). It's been sitting on my dresser for about 2 months being unused as I had no microSD cards in hand. All it had was an unlocked bootloader and working TWRP.
As of right now, I've tried to install 4 ROMs. All 4 did not work. I followed the instructions and unlocked my bootloader and did all other essential things. I installed ViperOneM8 before being ignorant that my WiFi wouldn't work. It was the only ROM I installed that actually booted properly. The only issue was that I had no WiFi. Had it worked, I wouldn't be making this thread. Then I got Android Revolution HD, installed it and it installed properly. I booted it into system, and it brought me to bootloader. This was the same issue I had while trying to install my first ROM, and still happens. Then I got CyanogenMod, and it didn't even install. TWRP told me it failed right off the bat. Same thing with whenever I tried to install a stock firmware recovery of the variant I have, HK Sprint.
Right now, I'm getting the 4.2.5 HK RUU in hopes that it works. I tried it previously, and it was a literal waste of time. I've been here for 5 hours trying different ROMs and to no success. I was very faithful I would get to use my phone again, although unless this RUU actually works, I don't have a lot of positive faith for my phone.
Are there any fixes for getting something like CyanogenMod to work? I actually really wanted this ROM after I remembered it, and was quite let down after it failed to work. Also, is there anything I should do with the phone before I go farther with anything?
Thanks for any help you all can give, I would greatly appreciate it. Sucks not having a phone, so I'll take any help I can get. Thanks once again!
EDIT: The RUU did not work. It failed to update. Waiting for answers I guess..
Click to expand...
Click to collapse
Flashing RUU requires locked bootloader.
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
F0rZ3r0 said:
Alright, I'm seriously about to just throw this thing in the dumpster. I've been here another 2 hours trying to get Cyanogen to work, and I figured out the issue with it. The updater script file wasn't accepting m8_whl. I'm still unaware how in the Mod Edit I'm supposed to put m8_whl into the script for it to be accepted.
To be more specific, the actual updater script has m8whl, while my phone recognizes as m8_whl. It denies it.
I thought I put it into the script correctly, although it is not accepting it. I found a quote not saying the location, and I assumed in the latest release of Cyanogen 12 for M8s, it was in /META-INF/google/android/updater-script
Please, someone help me before I have an anger episode. This thing has literally wasted my whole Mod Edit day.
Click to expand...
Click to collapse
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Alright, doing this now. I'm a lot calmer today, so I can do this.
dopy25 said:
Don't toss it, it's still worth something, even if not to you. But as @popthosegaskets said, you need to relock the bootloader to flash the RUU. If it's been sitting for awhile, what version of firmware and hboot was it on prior to not working? Perhaps the issue is that it's older, also try flashing the newest version of TWRP if you still want to install a custom OS.
If you want to RUU, just use the fastboot command "fastboot oem lock" while in fastboot and then run the RUU. I think it reboots after locking.
Click to expand...
Click to collapse
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
F0rZ3r0 said:
Didn't work, the RUU gave me the same error as last time, it tells me its the wrong RUU. Got both the stock RUUs just to see if I got it wrong about HK, both failed. Please help...
Click to expand...
Click to collapse
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Sloth said:
[Mod hat on] I know it can be frustrating at times but please take it easy with the swearing. [/Mod hat off]
You might try flashing the Full firmware that matches the RUU that you are trying to flash, the past couple updates require hboots to match on both your device and the RUU or you will get an error.
Click to expand...
Click to collapse
My apologies for the swearing, was angry at the time.
Also, my hboot version seems to be 3.18. Not sure what to do in order to be able to flash firmware. My OS version seems to be 2.16.651.4 as well if that helps.
What would I have to do in order to install a ROM and how?
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
dopy25 said:
If you are not flashing the full firmware to begin with, that's the issue. From your OP it looks like you only have an unlocked BL and had TWRP.
You must relock the BL and then run the full RUU, you can get it in the thread here, or get it from HTC. Either way you need the full one, it flashes the FW and Software as well as bootloader and radios.
HTC: http://dl3.htc.com.s3.amazonaws.com..._NV_SPCS_1.52_003_release_446220_signed_2.exe
Thread with all and modified FW
http://forum.xda-developers.com/showthread.php?t=2729173
Are you S-Off or On? If you are running the *.651* then that's the non HK version. It's ok if you flashed a modified stock, but if you got that from an RUU, that would be what the issue is. I think
Click to expand...
Click to collapse
I believe I'm S-OFF.
F0rZ3r0 said:
I believe I'm S-OFF.
Click to expand...
Click to collapse
look in bootloader it will tell you if you are s-off or s-on.
Sloth said:
look in bootloader it will tell you if you are s-off or s-on.
Click to expand...
Click to collapse
Never mind, S-ON.
F0rZ3r0 said:
Never mind, S-ON.
Click to expand...
Click to collapse
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Sloth said:
Ok re-lock your bootloader if you have not already.
Flash this for Non HK 4.25.651.18 Full Firmware
Flash this for HK 4.25.654.18 Full Firmware
Instructions:
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Once done flash the latest Non HK or HK RUU found here... http://forum.xda-developers.com/showthread.php?t=2729173
Then unlock your bootloader again using the unlock code you got from HTC.
Re-flash the latest TWRP found here... https://dl.twrp.me/m8/
This will give you a fresh start then you can try to flash the rom you want.
Click to expand...
Click to collapse
Umm...I don't have anything called SDK :/
What do I do then?
F0rZ3r0 said:
Umm...I don't have anything called SDK :/
What do I do then?
Click to expand...
Click to collapse
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Sloth said:
If you have a platform-tools you can use that or use the folder attached.
Unzip it and copy the files to a folder.
Click to expand...
Click to collapse
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
F0rZ3r0 said:
Alright, I did it all, but it doesn't seem to be changing once I send over the zip. Is it meant to take a while or is there something wrong?
EDIT: 20 minutes later and still at the sending. Something probably went wrong.
EDIT 2: 30 minutes later, still sending.
Click to expand...
Click to collapse
Should only be a few seconds.
Sloth said:
Should only be a few seconds.
Click to expand...
Click to collapse
Not sure what the issue here is then. As I write this, it is still sending. I'm not sure what the issue is...
Check PM.