So I've managed to acquire the OTA for my CID (HTC__K18) but I can't seem to be able to flash it. There is no RUU available.
I've got as far as flashing the firmware.zip, which worked, but not the ROM itself.
Even with stock recovery and boot, when I tried flashing the rom as update.zip through the stock recovery it just says 'OEM:00' and reboots normally.
Any idea what I'm doing wrong?
Can I use customRUU to flash it? Any idea how?
(Clarification: This is NOT a JellyBean update, it's 4.0.4 and the reason I want to flash it is I need to turn it in to repairs and I want to go back to stock).
Related
Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards
I have a nandroid backup of the stock ROM...it's rooted though.
Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.
Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.
...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...
Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.
How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.
I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.
... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com
as the title said, this is a good solution to get back to stock and to OTA update.
1- just download the awesome stock rom that made by mike1986 here http://forum.xda-developers.com/showthread.php?t=1546970&highlight=htc+one+x+*stock* (remember, the odexed one)
2- upload it to your SD
3- flash it normally as any custom rom using the CWM 5.8.4.0
4- flash the stock recovery which can be found at the same ROM thread (fastboot flash recovery recovery.img)
5- flash the stock boot.img, can be found at the same ROM thread (fastboot flash boot boot.img)
6- reboot
7- after rebooting, go to settings, about, software update
8- enjoy
just remember that it seems that mike's STOCK ROM already the latest updated one, so the update won't work till HTC officially releases the jelly bean.
dont forget the thanks button below
1.) is it necessary to lock the bootloader to install the OTA?
2.) i have a stock nand backup from my rom 1.29.
yesterday i flashed the boot.img from backup and restored the backup. after start my HOX came up with OTA update. so does i neet the original recovery.img too?
if yes which one can i take?
BR
1- actually i think relocking your bootloader is a must when u r running the original RUU, but here this is a stock rom to be flashed from ur CWM.
installing OTA just requires the stock boot.img and stock recovery, no need to relock the bootloader.
2- this is a fortune for me, wish i could have mine as well, then why not to restore it and get ur original OTA?
if your HOX updated the OTA already then no need to stock recovery, BTW your stock recovery can be found inside your origional RUU which can be found on filefactory server, am sure u've seen it before (just google how to extract RUU, then extract your stock recovery from it)
Hossam.Abdelsalam said:
1- actually i think relocking your bootloader is a must when u r running the original RUU, but here this is a stock rom to be flashed from ur CWM.
installing OTA just requires the stock boot.img and stock recovery, no need to relock the bootloader.
2- this is a fortune for me, wish i could have mine as well, then why not to restore it and get ur original OTA?
if your HOX updated the OTA already then no need to stock recovery, BTW your stock recovery can be found inside your origional RUU which can be found on filefactory server, am sure u've seen it before (just google how to extract RUU, then extract your stock recovery from it)
Click to expand...
Click to collapse
thanks i think you helped me
that was the plan... restore the backup and then do the OTA but i´m not sure if i could install the original OTA that way or i need to flash the original recovery.img too.
maple85 said:
thanks i think you helped me
that was the plan... restore the backup and then do the OTA but i´m not sure if i could install the original OTA that way or i need to flash the original recovery.img too.
Click to expand...
Click to collapse
hi
u need to get stock recovery and re lock ur phone or else the OTA wont get installed i just did it today
see this my post on the same : http://forum.xda-developers.com/showpost.php?p=32368798&postcount=112
I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware
So I found my old M83 the other day. It's running:
S-ON, UNLOCKED BOOTLOADER (NOW RELOCKED) ON TMOBILE.
I decided to try and flash the latest firmware via the sd card method, didn't work. Then tried flashing the firmware via fastboot. Fastboot didn't work either.
Now the phone only boots to the bootloader/hboot screen.
Any attempt at trying to flash firmware, or a recover, customer or otherwise fails.
I'm really hoping I can find a tmobile ruu zip to bring it back to life, however I can't seem to find a tmobile ruu zip anywhere anymore. I don't have a PC so downloading the *exe files doesn't do me much good.
Is there anyone that can please offer some assistance?
Much appreciated in advance!
What I did was to use TWRP and restore my original copy of the ROM (hopefully you still have that), if not you will need to find a TWRP backup of the ROM for the version of firmware you have and then restore the recovery for that same version (it get rid of TWRP). Then let the OTA fix update your phone. This is the route I took. Since Android 6 (MM) is the last release once you get to that stock, you can then replace the recovery (you could backup the recovery also) with TWRP, take a backup and then root or flash a new ROM.
Good luck
Greetings everyone! I just got the phone and it is great, but I have bit of an issue. I know that we need the stock recovery for the software updates, so I attempted to extract it yesterday. I could not do that since we need root to do it, and the only way to get root is by flashing TWRP. So I took the plunge, flashed TWRP, have root, but no stock recovery available.
Today I got an update notification that I cannot apply without the stock recovery IMG. Has anyone been able to extract it or get it from stock firmware files? I have searched the Internet quite a bit and I cannot seem to find the Stock files of this phone. Thanks for the help!
There is no Full Firmware Package-no Stock recovery.
You can test it from AL10 China Version,in Firmwarefinder found the full Firmware,does this not work,install Twrp back and wait for full Firmware