Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.
NextNexus said:
Does anyone know if it's possible to convert the HTC One M8 to a developer edition version? I've tried searching online and see that it was a possibility on last year's M7 but can't find anything specifically about the M8. Thanks.
Click to expand...
Click to collapse
Yes, it's possible.
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
garyd9 said:
Yes, it's possible.
Click to expand...
Click to collapse
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.
Thanks. Can you provide more detail on how to accomplish this or refer me to a thread that has that info?
Click to expand...
Click to collapse
I was typing.
Either will work, does not matter if its BS_XXXX1 or BS_XXXX2 as long as its the Brightstar cid, has no bearing on software whatsoever or the functionality of the software or phone...the ota comes with both so either will work regardless.....lol
garyd9 said:
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
.... The reason for installing the older firmware version was to "test" the system by allowing the OTA to happen. If the OTA fails, then you screwed up the above steps.
I was typing.
Click to expand...
Click to collapse
garyd9 said:
I guess you want some details, huh?
You'll need to get a Developer Edition stock recovery and a Developer Edition nandroid backup. (I'm lazy, so will just use "DevEd" instead of Developer edition.)
To get BOTH of these things, hop on over to a thread in the non-carrier specific M8 section: http://forum.xda-developers.com/showthread.php?t=2701376
Find and download the nandroid (TWRP) for CID BS_US002. Specifically, you should get the 1.12.1540.17 version. (There's a good reason for getting the older version...) You should also get a current TWRP image. (.img, not a zip file.) If you don't know how to get this image, then I'd advise NOT converting your device.
Then you can follow these steps:
Boot your phone normally.
Unpack the TWRP nandroid and place the folder into the proper directory on your phone's sdcard (/sdcard/TWRP/Backups/SERIAL_NUMBER/ or /sdcard2/TWRP/Backups/SERIAL_NUMBER) Replace "SERIAL_NUMBER" with your device's serial number. You should end up with a folder structure similar to: "./TWRP/Backups/HTXXXXXXXX/BackupName/" with the actual backup files in that directory.
... at this point, you might want to go ahead and boot into TWRP recovery to make sure that the backup you put in there is visible. It's fairly common for people to put the nandroid in the wrong place. I even did that myself once....
reboot into fastboot mode.
change CID to BS_US002 (BS_US001 is the "unlocked" version, BS_US002 is the DevEd version): fastboot oem writecid BS_US002
If you're starting with an AT&T branded device, there's no need to change the model ID (MID) as it's identical to the DevEd device.
reboot back into fastboot (to make sure the CID change worked): fastboot reboot-bootloader
use fastboot to put the proper DevEd STOCK recovery in place: fastboot flash stock_recovery.img
Probably not needed, but while in fastboot go ahead and run this: fastboot erase cache
Use fastboot to boot into (but not flash) the appropriate custom recovery. Example: fastboot boot openrecovery-twrp-2.7.0.2-m8.img
Use the custom recovery to wipe the data/cache/dalvik cache partitions.
Use the custom recovery to do a full restore from the backup copied to the phone above.
Reboot to the normal system. You can now accept OTA's and they should work. (They did for me.)
Click to expand...
Click to collapse
Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.
DG4FREE said:
Worked for me as well. Downloading the OTA as I type this. Thank you for the detailed instructions. Attempted to do this before when coming from the GPE ROM and had several issues. This time was much more streamlined thanks to your input.
Click to expand...
Click to collapse
Do I need to do anything different if I have twrp installed with stock Rom?
Alaris said:
Do I need to do anything different if I have twrp installed with stock Rom?
Click to expand...
Click to collapse
Stock rooted ROM or stock non rooted or stock Android (GPE or other ROM)?
Essentially follow the directions above, especially making sure you boot into TWRP recovery prior to flashing to the developer recovery since you already have it installed and go through the option to restore the developer edition nandroid backup. If it gives you the option to restore now, you should be fine to continue with the steps above. In short:
Reboot to bootloader.
Change your CID to BS_US002
Flash the developer recovery from the link above.
**Boot** into TWRP recovery (with the developer recovery still being the "installed recovery" using:
Code:
fastboot boot /location of recovery/recovery.img
TWRP should now open as if it was installed and allow you to restore from the developer edition nandroid even though you technically still have the developer edition recovery installed.
Once it restores you can reboot the phone and you should be good to go. Upon connecting to WiFi I was prompted to update to the latest OTA and everything has been working all day.
Sent from my HTC One_M8 using Tapatalk
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Thanks debating on stay with att stock or this for faster updates.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Its been great for me so far. I was on GPE and the little hardware issues (M8 is just better with Sense) made me come back. I've rocked the Maximus HD 4.0 ROM over in the open M8 forum and it has full AT&T support but thought I'd try this out. Sometimes I think the custom Roms put to much extras packed in although Maximus is decently light.
Sent from my Nexus 7 using Tapatalk
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
DG4FREE said:
Its been great for me so far. I was on GPE and the little hardware issues (M8 is just better with Sense) made me come back. I've rocked the Maximus HD 4.0 ROM over in the open M8 forum and it has full AT&T support but thought I'd try this out. Sometimes I think the custom Roms put to much extras packed in although Maximus is decently light.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Alaris said:
Thanks everyone had a couple of speed bumps but I got through it. Just out of curiousity would there be any difference between the Dev Ruu and doing this?
Click to expand...
Click to collapse
Wasn't aware of a Dev RUU being posted (at least an official one) but from what I understand it'd be the same thing.
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:36 PM ---------- Previous post was at 08:34 PM ----------
Roefastford said:
Dumb question ?
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
No AT&T branding/bloat. I know there's Roms out there that are debloated but you'd still be required to manually flash updates and or use the built in OTA of that ROM if it has such a feature. This in a way gives you the best of both.
Sent from my HTC One_M8 using Tapatalk
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Roefastford said:
What would be the main benefits to changing to lets say from the at&t m8 to a dev edition, other than faster updates ?
Click to expand...
Click to collapse
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
Alaris said:
Anyone notice the red writing during setup that said something along the lines of this being a test device and HTC will collect info like location etc.? Is this something that I should be worried about?
Click to expand...
Click to collapse
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
garyd9 said:
Assuming you're comparing "stock" to "stock": No carrierIQ, faster updates, no AT&T bloatware. (However, you lose Isis and the visual voice mail integration.)
I never noticed that. My understanding is that the warning comes up if you're using a recovery or kernel that doesn't match the rest of the firmware. If you follow the instructions I posted, you should end up with a completely stock recovery + kernel, so won't see that red warning.
Oh, and if you DO see the warning, it's completely harmless.
Take care
Gary
Click to expand...
Click to collapse
Do you have s-off?
Alaris said:
Do you have s-off?
Click to expand...
Click to collapse
Yes.
Sent from my HTC One_M8
garyd9 said:
Yes.
Sent from my HTC One_M8
Click to expand...
Click to collapse
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom. Do you see any red writing that says HTC will collect data? Because i did exactly what you did and I have that writing that says the will collect data and i cant opt out of it. It doesn't sound like me and you have anything that we did differently unless you didn't notice yours during the initial setup.
Alaris said:
Do my a favor go to settings>about and there should be one that says tell HTC click it and scroll to the bottom.
Click to expand...
Click to collapse
I don't have anything like "tell HTC". I did go through everything in settings->about, but nothing like what you described.
Sent from my HTC One_M8
I don't get why I that then
Sent from my HTC One_M8 using Tapatalk
Related
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Nilpo said:
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Click to expand...
Click to collapse
Maybe Unroot and try.......
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
[email protected] said:
Maybe Unroot and try.......
Click to expand...
Click to collapse
Is there a way to unroot without losing data? I haven't found one yet.
ryandroid226 said:
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
So there's no way to update and run a custom recovery? If I have to relock the bootloader, I can't unlock again without factory wiping.
Why can't HTC just get the bluetooth right from the start? How did they even release a phone when BT doesn't work?
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
Yeah u can unroot using SuperSU App itself from the setting choose Full Unroot........
Unintsall all the root Apps too since it unnecessary to have then without root.......
Flash the Stock recovery and relock the bootloader and then check for updates.....:good:
ryandroid226 said:
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
The unlocking will wipe ur Storage.....but u ll have the update of 4.2.2..
there are few Custom ROMS with Sense 5 u can go through this Forum
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
If you update via the OTA then your factory firmware WILL be updated. Maybe you can request that a dev make a ROM that is stock and rooted sense5/JB 4.2.2, you might grab the interest of someone.. That way you could have a "stock" image of the ROM and avoid the radio/hboot upgrade. Otherwise, you will just have to go through the update process, wiping your device. IMO, backing everything up is not too painstaking and it is a good practice to do this periodically anyways. Just my .02!
Sent from my HTC One X+ using xda app-developers app
Backing up isn't too difficult on JB. I've done it manually as well as with Helium and other apps throughout the rooting/experimenting process. It's been my experience that those app backups don't restore properly and I'm left starting over anyway. The issues could be app specific, but I honestly don't remember which apps didn't work now.
Of course, I suppose it's all a small price to pay to have a phone that actually works when I connect my BT headset.
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
mrbillishere said:
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
Click to expand...
Click to collapse
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Nilpo said:
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Click to expand...
Click to collapse
OK, well after dusting off the cobwebs and reading some threads for the Intl version I learned this... the stock firmware will also contain the radios and stock recovery. So now I'm looking for the correct firmware to match my phone's CID and Modelid. The command to dump these variables out is 'fastboot getvar all'
My AT&T OneX+ reported this:
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
There's a txt file in the firmware.zip that will contain a list of the applicable CID numbers the firmware can apply to. Evidently since our phones are S-on an entry in the list must correspond to the device's reported CID.
So now I'm searching for an updated firmware.zip
You can find the stock rom here as found in this thread.
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
There is no real difference between AT&T Kitkat and Jellybean on the One. In fact there are a few bugs with Kitkat. Such as the camera and a few others that have been posted.
njaustin123 said:
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
Click to expand...
Click to collapse
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
I dont want AT&T again
mb_guy said:
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
I dont want AT&T again.
njaustin123 said:
I dont want AT&T again.
Click to expand...
Click to collapse
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader here.
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it here.
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Thanks. Any more Info?
cschmitt said:
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Click to expand...
Click to collapse
Thanks a lot Schmitt. I think that is exactly what I have to do.
My bootloader is already unlcoked, Also I think I can handle Step 2 and Step3. Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
njaustin123 said:
Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
Click to expand...
Click to collapse
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
Go to http://www.htcdev.com/devcenter/downloads and select 'Brightstar US' as the carrier, then 'Find Files' and download the 'RUU 3.22.1540.1 Developer Edition'. It is an EXE, just run it with the phone connected to the USB port of the computer and it will walk you through the install. After it reboots you will have developer edition 4.3, then update to 4.4.2 by OTA, just check in the Software Update menu in settings on the phone. It will download a file to the phone that will update it.
rumrunner didn't work
cschmitt said:
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
.
Click to expand...
Click to collapse
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
njaustin123 said:
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Click to expand...
Click to collapse
Flash the ElementalX kernel from here http://forum.xda-developers.com/showthread.php?p=40682393 and try again.
It's unsecured and should make rumrunner successful.
Thanks. It's S-OFF Now
cschmitt said:
Flash the ElementalX kernel from here and try again.
It's unsecured and should make rumrunner successful.
Click to expand...
Click to collapse
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
njaustin123 said:
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
Click to expand...
Click to collapse
See, this stuff is easy. You'll like the Dev Edition ROM.
In Dev Edition
cschmitt said:
See, this stuff is easy. You'll like the Dev Edition ROM.
Click to expand...
Click to collapse
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
njaustin123 said:
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
Click to expand...
Click to collapse
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
How do I flash stock recovery?
clsA said:
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
Click to expand...
Click to collapse
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
njaustin123 said:
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
Click to expand...
Click to collapse
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Could not find the recovery image
cschmitt said:
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Click to expand...
Click to collapse
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
njaustin123 said:
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
Click to expand...
Click to collapse
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Any idea where can I get it?
mb_guy said:
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Click to expand...
Click to collapse
Any idea where can I get it?
njaustin123 said:
Any idea where can I get it?
Click to expand...
Click to collapse
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
No. That doesn't have it
mb_guy said:
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
Click to expand...
Click to collapse
I just downloaded it and checked, it doesn't have the recovery.img
I have bootloaders unlocked, S-off, root and TWRP 2.7.0.0 installed. I am trying to install 2.7.1.0 but can't get it to install. TWPR manager says it did but really didn't. Any suggestions?
Tubifex said:
I have bootloaders unlocked, S-off, root and TWRP 2.7.0.0 installed. I am trying to install 2.7.1.0 but can't get it to install. TWPR manager says it did but really didn't. Any suggestions?
Click to expand...
Click to collapse
fastboot. Search (in the HTC One (M8) sections) for "fastboot flash recovery"
garyd9 said:
fastboot. Search (in the HTC One (M8) sections) for "fastboot flash recovery"
Click to expand...
Click to collapse
Thanks that did the trick.
Tubifex said:
Thanks that did the trick.
Click to expand...
Click to collapse
Glad you found the fix. In the future, I would avoid any apps that install recovery. They aren't necessary, and tend to cause more issues than they solve.
And as you have found, as long as you have adb setup (and if you are modding the phone, you should), installing recovery is as simple as putting the file in your fastboot folder and typing a single command.
And while not the issue in the particular case, its sometimes useful to wipe cache before flashing custom recovery. I have seen quite a few instances where flashing recovery fails repeatedly and was easily resolved simply by wiping cache:
fastboot erase cache
New to the One M8, came from Galaxy S3, and feeling a little lost. I'm bootloader unlocked, s-off'd, custom recovery'd, and rooted but have a question. Can someone confirm the correct TWRP verison I should be using is for the M8 (GSM)? I flashed an older version of TWRP because it was referenced in an exact AT&T HTC One thread, but wanted to updated to 2.7.1.
Just want to confirm this is it: http://teamw.in/project/twrp2/225
johnhazelwood said:
New to the One M8, came from Galaxy S3, and feeling a little lost. I'm bootloader unlocked, s-off'd, custom recovery'd, and rooted but have a question. Can someone confirm the correct TWRP verison I should be using is for the M8 (GSM)? I flashed an older version of TWRP because it was referenced in an exact AT&T HTC One thread, but wanted to updated to 2.7.1.
Just want to confirm this is it: http://teamw.in/project/twrp2/225
Click to expand...
Click to collapse
That's correct. And you're not too lost if you did all that!
Thanks! True, but was used to Odin. The terms here s-off (still not sure what that is) and RUU's (I believe factory images) are new to me.
redpoint73 said:
That's correct. And you're not too lost if you did all that!
Click to expand...
Click to collapse
johnhazelwood said:
Thanks! True, but was used to Odin. The terms here s-off (still not sure what that is) and RUU's (I believe factory images) are new to me.
Click to expand...
Click to collapse
Every manufacturer has its own idiosyncrasies; and in fact even every device (from the same manufacturer) is often different when rooting. For instance, I used HTC devices for years before getting a Sammy tablet, and had little or no idea what Odin was! So every device is going to have its learning curve (and even more so if switching brands).
S-on/off is an HTC specific flag. S-off means "security off" which is a mode intended for HTC engineers which in theory turns off all protections and safety checks on the device (and the reason its so valuable to modders).
RUU is "ROM Update Utility" which is an program that (as you surmised) installs or restores a complete device image including bootloader, radio, ROM, and other modules. Again, its an HTC specific thing.
You rock! Thanks for the clarification.
Sent from my HTC One_M8 using XDA Free mobile app
Howdy folks...so my buddy picked up an M8 off of Craigslist that was apparently running some sort of vanilla android. It is unlocked and S off..he attempted to flash a Sense ROM and ended up in a boot loop. He's the kind of guy that shouldn't be doing such things...
This is where I come in to the rescue. After some reading this afternoon, I've come to the conclusion he must have a GPE converted phone. I personally have no experience with this device (G2 Verizon owner) but I'm pretty versed in fast boot and ADB.
The phone is currently in fast boot. This is all it has. If I attempt to boot it into recovery, it loops.
Can anyone help me get this thing running by pointing me in the right direction? Ideally, I'd like to have it fully AT&T stock.
My current plan was to push a recovery via fast boot and flash a GPE ROM off of SD. Will this work?
I just don't want to mess the phone up any further.
m8
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
passion8059 said:
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
Click to expand...
Click to collapse
Yes, bootloader is basically all I have. Thank you for the help!
I won't be able to get to work for a few hours, but I'll update with any progress.
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
m8
mulhiny said:
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
Click to expand...
Click to collapse
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Hope this helps!
passion8059 said:
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Click to expand...
Click to collapse
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
redpoint73 said:
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
Click to expand...
Click to collapse
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
passion8059 said:
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
Click to expand...
Click to collapse
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
redpoint73 said:
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Click to expand...
Click to collapse
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
passion8059 said:
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
Click to expand...
Click to collapse
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
pclaunch said:
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
Click to expand...
Click to collapse
Yes.
Keep in mind, if you are s-on, you need to have the proper CID or SuperCID. Plus, you can only run an RUU with equal or greater hboot number than the hboot presently installed on the phone.
S-off should bypass both these issuees (CID and hboot version check).
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.