Related
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
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
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
shepppster said:
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
Click to expand...
Click to collapse
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
https://www.androidfilehost.com/?fid=95897840722644637 - Thanks to LIabtoofer
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -http://techerrata.com/browse/twrp2/m7
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
an0ther said:
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
Click to expand...
Click to collapse
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
shepppster said:
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
Click to expand...
Click to collapse
I do not recommend you just grab the latest firmware update and flash it to you phone, There is a very good chance you will brick your device with a firmware incompatibility
As your on 2.xx firmware jumping strait to 6.xx or 7.xx is a big jump and skipping firmware updates should never be recommended.
To safely update your firmware you need to flash 3.xx, 4.xx, 5.xx and so on untill your updated to the latest firmware. I was able to find the 5.xx and 6.xx firmwares for your device here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/161/ but you will still need to find 3.xx and 4.xx. ALternativly because your s-off with super cid you could switch to a different firmware brand HTC 401 for example. all of which can be found here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you will need to flash atleast these 4 updates to get to the latest safely
3.62.401.1
4.19.401.11
5.11.401.10
6.09.401.12
On the other hand if your not comfortable flashing firmware you could just install a Guru Reset rom then update your phone through OTA updates although that will take much longer than flashing the firmware manually. This reset rom will give you stock with working OTA's if installed with the following options http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
Stock Recovery = Yes
Stock Radio =Yes
Root = No
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
shepppster said:
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
Click to expand...
Click to collapse
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
shepppster said:
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
Click to expand...
Click to collapse
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Danny201281 said:
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
shepppster said:
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
Click to expand...
Click to collapse
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Danny201281 said:
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Click to expand...
Click to collapse
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
shepppster said:
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
Click to expand...
Click to collapse
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Danny201281 said:
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Click to expand...
Click to collapse
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
shepppster said:
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
Click to expand...
Click to collapse
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Danny201281 said:
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Click to expand...
Click to collapse
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
shepppster said:
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
Click to expand...
Click to collapse
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
Click to expand...
Click to collapse
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Danny201281 said:
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Click to expand...
Click to collapse
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
you don't have to delete anything from the firmware's just flash them sequentially till you get to the last one
then just flash TWRP and your rom to the phone
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Danny201281 said:
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Click to expand...
Click to collapse
I already have it on my internal memory and also on a USB stick via OTG lead,and in my Fastboot folder (so 3 options).
I Will have to re-install/flash img of TWRP again (if i didnt delete the recovery in the firmware zip files and,as the firmwares will give me stock recovery)- reboot into bootloader launch TWRP recovery find the rom on SD or push in adb or flash from memstick...but job done!
Any issues installing TWRP over an old one? (I intend to use the same version as I have now) I assume it will see the old TWRP folder and old bkup in the SD card too? if not I am goin for it!
Shepps
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
shepppster said:
Hi,
I was in the process of flashing new firmware (iI have a thread for this when asking advice and followed the steps on my previous thread) I was flashing firmware 5.11.401.11 which loaded succesfully and rebooted to bootloader.
When it rebooted a driver message cam up I think regarding Qsub or something and the device has frozen or dead.
In the command window it says "wating for device"...i cant seem to get it to do anything!!
My device shows as other devices in my computerQHSUSB-DLOAD and the message I recall was about drivers ...do i need to update them?
Any help please?
Shepps
Click to expand...
Click to collapse
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
Ok the unbricking has worked so far....can someone confirm the fastboot commands in Linux are the same as on a windows CMD prompt please?
I dont want to get this far and not flash the firmware properly.
Danny201281 said:
Seem's like you may have skipped an important firmware update, which firmware number were you updating from?
If you skipped a firmware version e.g 3.xx.401.x to 5.xx.401.x then you will be needing the Unbrick project here http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
shepppster said:
Is there a guide on the forum for using Linux so i get the last part (Flashing firmware) perfect please?
Click to expand...
Click to collapse
Fastboot works just the same in Linux as in Windows with the exception of you must use "sudo"
So
Code:
fastboot devices
becomes
Code:
sudo fastboot devices
Code:
fastboot flash zip firmware.zip
becomes
Code:
sudo fastboot flash zip firmware.zip
and so on if you forget to use sudo you will just see "waiting for device" in which case press ctrl+c to cancel and do command again with sudo :good:
shepppster said:
I did go consecutively fro 3-4-5 but..I guess It happens. The firmware seemed to flash ok.
I will try the link.
Thanks
Click to expand...
Click to collapse
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
shepppster said:
What actually happened is when I was flashing from 4****** to 5***** when I tried to reboot to booloader my PC wanted to reinstall device drivers ,which I think I cancelled by mistake causing the hang up?
I have unbricked and now in bootloader waiting for the device to recharge fully.
I have then got to flash the 5****** series of firmware again(as instructed by the unbrick software).
I will then either install a custom recovery and flash my jellybean back-up or a custom ROM, do you think ARHD 84 will install on the 5***** firmware? I dont fancy going to 6**** until all is ok.
Or is there a way of flashing a stock o/s that can be flashed from TWRP? for the WWE firmware?
Shepps
Click to expand...
Click to collapse
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
shepppster said:
Ok I have unbricked my device and used TWRP to recover my back up....however after flashing up to 5******** firmware ,the firmware seems to have reverted back to the 2******* series I started with??? Is that correct?
If so I have to start all over again?
Click to expand...
Click to collapse
no firmware does not revert back .. where are you getting these files ?
clsA said:
no firmware does not revert back .. where are you getting these files ?
Click to expand...
Click to collapse
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
shepppster said:
This is the information from my phone the "about" section in settings. software number 2.24.161.1 i havent gone as far as a getvar cmd in fastboot yet,if thats where the correct info will be?
Click to expand...
Click to collapse
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Danny201281 said:
I see in the Unbrick Project Thread your device is fixed But for the record the Software Number in settings is the software number of the rom not the firmware :good: Glad to hear your back up though good job. :highfive:
Click to expand...
Click to collapse
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
shepppster said:
Ah I thought it might be...all I need know is to move to 6**401 firmware so I can flash the latest ktkt roms (not lolipop) I was a bit of a mare but find it easier to my Ubuntu pc as I dont have to worry about drivers and the like.
Thanks Danny
Click to expand...
Click to collapse
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Danny201281 said:
No Problem, And yeah i'm a Linux user myself and it is the shizzle when it comes to android phones
Click to expand...
Click to collapse
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
shepppster said:
I intend to carry on where I left off...I havent got as far a flashing the new rom.
The 401 firmware I am using is currently 5.11.401.10 ,next step is the 6 series.
Is it best to flash 6.09.401.5 then 401.10,401.11,401.12 consecutively or jump straight to 12?(clearly I dont want to go through the bricking stuff again!!)
Is there a link to a good source of firmware,i looked on the Vomer guide but they are decribed as the dual simHTC one at the download page, is this going to be an issue as I will get them from there as a reliably good source?
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Danny201281 said:
I know that some have jumped strait to the latest without any problems and the theory goes as Lon as you don't skip a version number e.g 3.xx to 5.xx then it should be safe.
Obviously the safest option is to flash each update so you know your not missing anything important. As for a good source I prefer to stick with HTC signed firmware from official OTA updates all of which you can find here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Click to expand...
Click to collapse
@Danny201281 and @clsA Thanks for all your help...successfully flashed up to the latest 6******** firmware and flashed a custom rom.
Perhaps minscule to u guys but massive step forward for me !
Few nailbiting moments anticipating a brick again..but it worked fine using Ubuntu which is much less finicky than windows to use and my weapon of choice from now on!
:good::good:
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great. What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Thanks
AJHylton said:
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great.
Click to expand...
Click to collapse
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Click to expand...
Click to collapse
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
alray said:
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
Click to expand...
Click to collapse
I'd like to add - change recovery to TWRP as it's recomended for most ROMs out there
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
AJHylton said:
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
Click to expand...
Click to collapse
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
alray said:
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
Click to expand...
Click to collapse
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
AJHylton said:
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
Click to expand...
Click to collapse
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
alray said:
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
Click to expand...
Click to collapse
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
AJHylton said:
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
Click to expand...
Click to collapse
There is no RUU for 7.19.401.30 but there is one for 7.19.401.22 which can be used on your phone if needed in the future. :good: