Related
Hi I want to restore back to three uk firmware run my bootloader has been unlocked from htc dev unlock and I have a custom rom with touch recovery I have downloaded the stock uk three firmware run but not sure what to do next would appreciate some instructions.
1. Restore backup you made before flashing the custom ROM
2. Manually flash the stock boot.img
3. Manually flash the stock recovery
4. Relock bootloader (optional)
did not make backup so is there a plan b?
are you going back to stock to send phone off for repair?
If you are then run a backup of your current ROM from recovery first and copy SD to your PC for safe keeping.
1. Boot into fastboot
2. Flash stock recovery, found here (if you were on 1.26 before flashing custom rom then flash the 1.26 recovery, and 1.28 > 1.28): http://www.androidrevolution.nl/ARHD/index.php?dir=OneX/Recovery/
3. Relock bootloader: fastboot oem lock
4. Run RUU (phone needs to be in fastboot, and correct drivers installed onto PC for RUU to detect phone).
Edit: If you were on 1.28 before custom flashing then make sure you have the 1.28 RUU
Info found here: http://forum.xda-developers.com/showthread.php?t=1609190
thats the thing i dont know what it was on 128 or 126 i tried to flash the 126 ruu and it failed so i presume its going to be the 128 ruu file so does it mean i have to flash the 128 stock recovery aswell or does it not matter.
If the 3 UK 1.28 RUU is available then you just flash that as the recovery comes with it. Remember you HAVE to relock the bootloader to run an RUU
Well i ran the 126 ruu and it failed it said something like get the correct bootloader after i did all the steps flashed stock recovery and relocked bootloader.
jutley said:
Well i ran the 126 ruu and it failed it said something like get the correct bootloader after i did all the steps flashed stock recovery and relocked bootloader.
Click to expand...
Click to collapse
Have a look at your hboot version, if it is 43 then you probably have the 1.26 stock, if it is 94 then it should be the 1.28. I have the 1.28 3 RUU here, will see if I can find the download link for you.
Edit: Here is the post to the download link
my hboot reads 0.94.0000 so downloading 128 ruu thanks for the link so what stock recovery do i flash 26 or 28? i dont know what i had before.
jutley said:
my hboot reads 0.94.0000 so downloading 128 ruu thanks for the link so what stock recovery do i flash 26 or 28? i dont know what i had before.
Click to expand...
Click to collapse
you will need to flash the 1.28 recovery. unlock your bootloader first, then flash recovery, then relock again. you can use the same unlock.bin file that you got off HTCDEV to unlock the bootloader.
yep i already unlocked the bootloader just waiting for the download to finish and will post my results soon thanks for the help.
Thank you i can confirm this worked 100%
You're welcome
I'm going to update my htc one x to jelly bean from ICS, using custom ROM (ARHD), it was noted that I need a firmware package, and now that I found the package for my CID because took sometime before I found it, is it really required to flash it? TIA
For JB roms you need a JB hboot those are the 1.31 and higher up. Except for the aosp JB roms, those run also on the lower ics hboots.
So if you are on a lower hboot then 1.31 then yes you need to upgrade the hboot
Now I think everything's messed up and I badly need help here, so stupid with I did.
At one moment, my phone is stuck at One tm screen, after I flash the boot.img and installed the custom ROM. I tried to restore my phone using CWM but it still stucked. It was too late before I realized how to flash the firmware package that I need to rename what I downloaded to firmware.zip. I tried flashing the firmware without knowing that I have to relocked my phone before I flash it. Now I relocked my phone and I'm stucked with hboot and I can't do anything at the moment.
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zip
Once completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zipOnce completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cannot load "firmware.zip" always shows up. My CID is HTC_044, and as far as I know I downloaded the correct firmware package for my phone according to ARHD forum. Thanks in advance.
Did you have the firmware.zip in your fastboot folder?
Yes. And I downloaded it 3 times just to make sure it is the right firmware.
Oh and sometimes you need to flash it 3 or 4 times to succeed. I had to do the command 3 times when I flashed my firmware.
So try it multiple times in a row.
Sent from my One X
Sorry but I tried several times and "error: cannot load 'firmware.zip' all the time. What could be the problem?
During at work. I thought if is it possible just to return to stock ROM? But I just can't find the proper RUU yet.
cid: htc_044
version-main: 1.29.707.11
I'm currently charging my phone using the batch file I found here in xda. I saw a lot of posts regarding flashing the current version of CWM so you can charge your battery, I think my CWM is in version 5.8.1.0, and as far as I know you have to unlock your hboot before you can flash recovery, so it's impossible for me to flash 5.8.4.0? Am I correct here or I can just proceed to the other steps?
I can check tonight if i have your RUU !
Mr Hofs said:
I can check tonight if i have your RUU !
Click to expand...
Click to collapse
Thank you Mr Hofs! And, should my battery level is 30% or higher before I can flash the RUU?
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Mr Hofs said:
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Click to expand...
Click to collapse
I was done in re-unlocking my bootloader, but then I still can't flash cwm recovery because it says low battery, then I tried to use the batt script again and of course it cannot work since I just re-unlocked my bootloader.
I never tried it with a unlocked bootloader, have you tried it ?
Yes, I tried it and it doesn't work.
What I did for the past hours, I tried to restore my phone again using cwm recovery, still nothing changed, still stucked at htc one logo, then I turned it off trying to charge it using the main charger and it does have light in its LED, left it for a while and now it doesn't turn on.
Try it with phone connected to the pc, it seems to make a difference sometimes....and if you are capable again to run the bat script then leave it for 2.hours or so !
Now it's working. The first time I used the batt script, I thought it could charge more than 3681mV but It didn't work as it didn't get higher than 3681mV. I HOPE it's enough just to flash the cwm recovery. Thanks Mr Hofs, will update asap.
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
mcgrathpatj said:
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
Click to expand...
Click to collapse
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
xunholyx said:
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
Click to expand...
Click to collapse
It's fastboot flash recovery recovery.img
The first recovery tells the device the location to which you want to flash it, in this case "recovery" for the recovery partition and the second one is the file you wish to flash in this case "recovery.img".
---------- Post added at 07:26 PM ---------- Previous post was at 07:04 PM ----------
mcgrathpatj said:
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
Click to expand...
Click to collapse
Do you know what software version you were on?
Just try the Developer Edition RUU again. If you're S-ON which you are, then bootloader needs to be relocked. I can't think of a reason why it shouldn't work, even if recovery is gone it completely returns device to stock(Including recovery).
You don't have to do the CID/MID part seeing as you're S-ON and you need S-OFF to do that. I don't think you used the converted GPE but instead a GPE ROM
I donwloaded the RUU for the Develoer Edition and it errored out at 155. I must have tried this 5-6 times.
I think I finally figured this out, so it may be useful for someone else. Who knows.
1) I downloaded another users NANDROID backup from the Dev Edition from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
2) I flashed TWRP, restored the NANDROID from the above thread using TWRP.
3) Then, I flashed the original STOCK corresponding recovery from the same thread.
4) I was able to reboot and wifi FINALLY worked properly on a sense rom. I downloaded the OTA and it updated successfully, upon reboot through, wifi was broken again.
5) Re-locked the bootloader via fastboot oem lock, then performed the RUU for the Dev Edition from this thread here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
The RUU just completed successfully, so I think I'm out of the woods. But man oh man that was painful.
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.
Hello, I am using a rooted htc one m8. I wanted to unroot it and reverted my device to android KitKat. I flashed stock recovery from the official OTA of 5.1.1. after that I tried to lock the bootloader using the command "fastboot oem lock" command using adb. then I tried to update the phone to Android lollipop. It installed and the phone shut down. now when I try to switch on the phone, It boots to stock recovery. even I cant get unlock code for bootloader to unlock it again. Please help me to solve this issue...
can you boot to bootloader ??
if yes then post the result of fastboot getvar all ( remove serialno and imei before posting )
Affanthegreat said:
Hello, I am using a rooted htc one m8. I wanted to unroot it and reverted my device to android KitKat. I flashed stock recovery from the official OTA of 5.1.1. after that I tried to lock the bootloader using the command "fastboot oem lock" command using adb. then I tried to update the phone to Android lollipop. It installed and the phone shut down. now when I try to switch on the phone, It boots to stock recovery.
Click to expand...
Click to collapse
This is really confusing. In addition to the getvar data previously requested, you should outline step by step, what exactly you did (in detail, with file names, etc.). In particular, I'm very confused about:
1) What version number you started on (when you were rooted)?
2) How did you "revert to Kitkat", what files did you use, etc.
3) What stock recovery number you flashed
4) How/where you obtained the file to update after you flashed stock recovery and locked bootloader. Did it download automatically after you flashed stock recovery, or did you put it on the phone manually (if the latter, what version number and/or file name).
Also, the following should be kept in mind:
- You need a stock never rooted ROM/TWRP backup (unrooting won't work) and stock recovery in order to properly update by OTA.
- You do not need to lock the bootloader to install an OTA update, but you do need a locked bootloader to flash an RUU or firmware.zip. So depending on what exactly you used to try to update, locking the bootloader may not have been necessary; and may be causing you more trouble than good.