I have an AT&T HTC One M8 running KitKat, but I want to convert to stock Dev Edition and run Marshmallow, ridding of AT&T's bloatware.
I have S-Off and have unlocked my bootloader. I am trying to root at this point but am coming across technical difficulties (mentioned in post 2).
I know that I'll have to change the Developer's Edition carrier ID. My current CID is AT&T's CWS__001
Lastly, I'll have to run the Dev Edition RUU, which I don't know where to get.
As I am quite new to all of this, there are terminologies that I have an idea as to what they mean, but may not fully understand.
So as you can see, I have this general outline of what I think I may need to do. But since I actually do not know how to do them, I basically am in need of a guide. Hopefully someone can inform me if I'm missing any crucial step(s)!
I'm not sure what to do at this point, but I'm going to try to root my phone. I'll update my status on how it goes.
I cannot flash a twrp. Yes, I am on FASTBOOT USB on my M8's bootloader.
When I type in "fastboot flash recover m8recovery.img" on my Command Prompt, it says... error: cannot load 'm8recovery.img'
m8recovery.img is what I have named my...
Wait a sec... brb
Okay, so I had to type in m8recovery.img.img because I had it named with the .img
My mistake, I didn't know. However, I still have the problem of being stuck on the "Entering Recovery..." screen.
I'm gonna have to try different versions of twrp.
Edit: twrp version 3.0 and 2.8 was not working. I had to try 2.7 before it would work.
After flashing SuperSU, I've finally managed to root my device.
lxiong1 said:
When I type in "fastboot flash recover m8recovery.img" on my Command Prompt, it says... error: cannot load 'm8recovery.img'
m8recovery.img is what I have named my...
Wait a sec... brb
Okay, so I had to type in m8recovery.img.img because I had it named with the .img
My mistake, I didn't know.
Click to expand...
Click to collapse
Do yourself a huge favor , and go into Windows folder options, and disable the option to hide known file extensions (which is enabled by default).
lxiong1 said:
However, I still have the problem of being stuck on the "Entering Recovery..." screen.
I'm gonna have to try different versions of twrp.
Edit: twrp version 3.0 and 2.8 was not working. I had to try 2.7 before it would work.
After flashing SuperSU, I've finally managed to root my device.
Click to expand...
Click to collapse
The proper version TWRP depends on OS version on the phone. Since you were still back on Kitkat, it would require an older TWRP (2.7).
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
lxiong1 said:
Lastly, I'll have to run the Dev Edition RUU, which I don't know where to get.
I basically am in need of a guide.
Click to expand...
Click to collapse
Guide to convert to Dev Edition is here: http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Although you don't need to change the MID (as the AT&T and Dev Ed versions already have the same MID), you just need to change CID. Then run the desired Dev Ed RUU.
MM Dev Edition RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
But it should also be noted that for the MM in particular, you will need to flash the firmware, then RUU (otherwise RUU will fail with Error 155: unknown error): http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
It should also be noted, that all the above info (guide, RUUs, etc.) can be found my Index Thread: http://forum.xda-developers.com/showthread.php?t=2751432
So in short, the next steps to convert to Dev Editions (since you already have s-off and root):
1) Change to Dev Ed CID with guide linked above
2) Flash 6.12.1540.4 firmware with fastboot
3) Run 6.12.1540.4 RUU
I managed to change my CID to BS_US002
But when I download and try to flash firmware.zip, I get: FAILED <remote: 42 custom id check fail>
Any idea what gives? I tried brushing it off and going for the RUU. But obviously after failing to flash firmware.zip, I got Error 155.
It sucks to get this far and not get Dev edition Marshmallow. Uhghh... what a drag
If I knew that I'd have to go through this ridiculousness, I wouldn't have purchased this phone.
lxiong1 said:
It sucks to get this far and not get Dev edition Marshmallow. Uhghh... what a drag
If I knew that I'd have to go through this ridiculousness, I wouldn't have purchased this phone.
Click to expand...
Click to collapse
You have to repeat the same command when you get failed. That's how you flash a firmware .
Sent from my HTC One_M8 using Tapatalk
Deleted message.
Okay, it seems that the reason why I get the "42 custom id check fail" error is because my CID is at BS_US002
The firmware.zip file that I have is for CID's that are on CWS__001 (yes, two underscores)
So a tip for those wanting to convert to (Android 6.0) Dev Edition: Flash firmware.zip first before changing your CID.
I will test this out and see if my conversion is successful. If I fail, then I'd assume it's because I need a firmware.zip... specifically for BS_US002
Hell... Flashing the firmware was a success now; but running the RUU (Dev Edition)... was not successful.
On the other hand, running the RUU (AT&T) will successfully update you to Android 6.0 Marshmallow.
So in conclusion, someone should show us where we can get a firmware.zip file that is for the Developer Edition. Because the firmware.zip from this link: http://forum.xda-developers.com/show...9&postcount=23
... is only an update for specifically the AT&T firmware, not for Developer Edition.
Right now, I am reading: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
And it says: take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly. That is helpful information and important for those who need it.
But for now, personally... the task of altering/modifying a file within a zip file and then redoing this whole process for developer edition doesn't seem worth it to me. And the reason why I say this is because AT&T's skin is not so bad on Marshmallow... Whereas on KitKat and Lollipop, it was intrusive. This is something I can live with. AT&T's skin is actually nearly non-existent if I root and remove bloatware.
lxiong1 said:
Hell... Flashing the firmware was a success now; but running the RUU (Dev Edition)... was not successful.
On the other hand, running the RUU (AT&T) will successfully update you to Android 6.0 Marshmallow.
So in conclusion, someone should show us where we can get a firmware.zip file that is for the Developer Edition. Because the firmware.zip from this link: http://forum.xda-developers.com/show...9&postcount=23
... is only an update for specifically the AT&T firmware, not for Developer Edition.
Click to expand...
Click to collapse
My apologies, you are right I linked the wrong firmware.zip (502 for AT&T, not 1540 for Dev Ed). You can find the 6.12.1540 firmware here:
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
In short, the requirement to run the firmware.zip is the same as an RUU, that it needs to match your CID and MID.
Related
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
I want to install an OTA, but I had rooted it using TWRP and then followed so many procedures in trying to restore to stock that I think my phone's wasted. (It's functioning normally, but I can't help the feeling I've done something untowardly to it).
I have been doing a lot of reading, but I apparently suck since nothing seems to make sense (or that everything seems so disconnected). It appears that what could be one long, detailed post about something is to be found in many different posts, but I understand that since there are so many phones and each one probably needs its own way of being handled. So without complaining any further, I'll just let you know what I've done so far, and hopefully someone is able to tell me what the hell is wrong with me. And my phone.
Here's what I have with me right now:
Device: HTC One SV (Boost mobile) - K2_CL, OS- 4.1.2 (the OTA is 4.2.2)
Tampered, relocked, s-on.
adb is installed
fastboot is installed
android SDK with 4.1.2 and 4.2.2 packages installed
htc toolkit utility is installed
recoverytest.img from androidruu files.
revone
All right, I installed adb, fastboot, an htc utility toolkit, downloaded 3 different img files (one says recoverytest.img, which is from androidruu.com/k2_cl, another one was put here on xda by one of the members, and that was simply recovery.img, and another one called HTC_One_Sv_K2_Ul_boot_signed.img <-- this is probably the wrong file since my bootloader screen says k2_Cl).
Prior to this, a few months ago, my phone was rooted. SuperSU was working fine, and one day somehow I lost the root access when SuperSU upgraded. Tried a few methods to upgrade manually but none worked. Not sure if this is of any importance.
So after installing all those above, I did a variety of commands like revone, fastboot flash recovery.img, fastboot oem lock, fastboot flash boot recovery.img, all based on what was mentioned one one thread or another on the forum and mostly all of them gave me some kind of an error.
So I'm stuck now. My phone does nothing. When I reboot from bootloader, it says in red "this is for development purposes only, blah, blah". When I download the update and try installing it, the phone simply restarts. When I try to do factory reset from the hboot, the phone simply goes back into fastboot menu. My phone apparently doesn't have an RUU, only a recoverytest.img.
Here's where I am and I want to do what next. I jsut installed android sdk, and installed 4.1.2 package (which is the current version on my phone), and I want to update to 4.2.2, which is the latest update for htc one sv on boostmobile (installed the package for that in sdk also).
(A lot of people were also asking for cid, mid and phone model, and I have no clue how to make sure that the .img file is the same as my phone's).
I know I am all over the place, and call me a knucklehead, but I genuinely do not understand a lot of the things that are mentioned on the forums. Every thread mentions a process, and within each process is contained a subprocess which I equally do not know.
Thanks for any help with this!
PS: While I go from fastboot usb to hboot, the screen flickers for a couple seconds an dmessages like "sd checking: no image or bad image" appear for a couple seconds and then I see the hboot menu.
Edit:
Here are some, but not all, of the forums/threads I was trying to follow:
http://forums.androidcentral.com/verizon-droid-dna/287135-revone-s-off-root-method-help.html
http://androidforums.com/one-sv-all...root-without-overwriting-recovery-kernel.html
http://forum.xda-developers.com/showpost.php?p=38018890&postcount=78
http://forum.xda-developers.com/showthread.php?t=2292432
http://forum.xda-developers.com/showthread.php?t=2405050
http://forum.xda-developers.com/showpost.php?p=42371333&postcount=1480
http://forums.androidcentral.com/htc-one-sv/279026-htc-one-sv-ruu.html
http://www.androidfiles.org/?developer=K2_CL
http://forum.xda-developers.com/showpost.php?p=43266179&postcount=6
The way I understand how to do this (in layman terms) is as follows:
1. Restore to stock {by first turning S-Off, then lock the bootloader, and then RUU. I cannot get S-off using revone (revone failed, error code 2 or error code -1); the bootloader is "relocked", and I cannot get to do anything with the RUU (iow I don't know what to do with it)}.
2. Restore to factory settings.
3. Download and install the OTA 4.2.2 update.
You don't need to go S-Off to return to stock, just relocked. Here is the RUU for your phone:
http://goo.gl/0cgV6d
Run as admin. Turn off anti-virus. Have more than 30% battery life. Follow instructions as the program loads and accept whatever.
OTA zip:
http://goo.gl/ckfYQj
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
ravisoni said:
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
Click to expand...
Click to collapse
You're welcome. It is the 4.2.2 update. My understanding is that there is nothing newer. There were reports of a 4.4 update for the Boost variant, but believe it was a mistake, or at least jumping the gun by quite a bit.
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
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.