I downloaded the 6.16.651.2 RUU and installed it on my Sprint M7 and I was wondering if there is anyway for me to get a backup or download the stock recovery before I flash TWRP. I was also wondering what the CID should be? I am worried that I have put the wrong CID into my phone. I had s-off but I turned it back on after I changed the CID.
Thanks
Related
All,
I have the Dev Edition with S-OFF and CID111111 running ARHD 13.3. With the latest update to the Dev Edition to 4.3, can I just flash the RUU for the latest of the Dev Edition? Will it work with TWRP custom recovery?
Thanks for any info.
Emh, the RUU isn't a zip, but an exe that you have to flash with the pc...
However, you can flash it
You can flash an RUU when S-OFF with Super CID, I've done it a number of times
The RUU is a complete update so it will overwrite the custom recovery anyway
Awesome guys....with that being said, I have a few more question. Since I'm S-Off and Super CID, you said I can flash any RUU, but it will wipe the custom recovery. That is fine, but when I want to flash a ROM in the future, I will have to reflash a new recovery correct? Will this mess with my HBOOT? I'm on 1.55 right now.
Also, I'm on the http://forum.xda-developers.com/showthread.php?p=39588860 looking at the collecdtion of RUU's...do I flash the ZIP, EXE or the Decrypted RUU's?
Again, thanks for your replies!
Download the RUU from HTCDev directly so you know you've got the right file, then flash it with the phone connected in fastboot. It will downgrade the HBOOT and put the phone back to 1.29.1540.16 and be just like it was out the box (except you'll still be S-OFF with Super CID). You can then get the OTA to .17 and then the OTA to Android 4.3...after that, you can flash a custom recovery and do what you want (but I'd take a nandorid first of course)
EDDYOS,
Thanks for all your info!! I will do exactly that!
One last question, I promise...since I am on S-OFF I should not be worried that flashing the RUU and downgrading to HBOOT 1.54 and not be able to achieve SOFF again? Cause isn't 1.54 having issues with SOFF? Or does that not matter to me since I have the Dev Editoin?
Again, thanks for all your advice.
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
EddyOS said:
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
Click to expand...
Click to collapse
EddyOS...
Thanks alot! Gotcha!
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
details
Bloodrave said:
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
Click to expand...
Click to collapse
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
cc999 said:
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
Click to expand...
Click to collapse
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
hboot
Bloodrave said:
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
Click to expand...
Click to collapse
Then your Hboot 1.44 may not be the correct one. PM me with your email and I will give
you the correct one.
CC
I have tried once again with the 1.44 Hboot and the zip from htc official website , the developer edition one.
Still no luck.
With the help of cc999 i managed to revert back to 4.3 Developer Edition.
Apparently there was a mess in my adb and usb drivers.
So i managed to install the 4.3 Developer Edition on another laptop and it worked just fine.
Thank you again cc999 for the support.
You should use the stock recovery to flash the ruu.exe. Makes life so much easier!
Sent from my HTC One using Tapatalk 4
Hello, I have a HTC One.
I was trying to upgrade my radio after installing a new custom rom using twrp. I accidently tried to install the fastboot version of the baseband instead of the recovery flashable version with twrp. The install failed. When I rebooted my phone I was not picking up any cellular signal. In the settings under Baseband version it says “unknown”, also says “unknown” for my IMEI.
I have tried:
- installing the correct recovery flashable version with twrp.
- restoring to my backup that was made before making any changes.
- restoring back to a stock Rogers rom.
I am still not picking up any cellular signal. I also, tried to do a full firmware/radio flash using fastboot, but I received a “remote: 41 model id check fail” error.
I got the radio files from the follow link:
http://forum.xda-developers.com/showthread.php?t=2485319
If anyone has any suggestions or know what else it can try it would be appreciated.
Device info:
- Rogers htc one that is carrier unlocked running Bell SIM
- Bootloader unlocked, Rooted, S-OFF
- TWRP version 2.6.3.3
- CID = ROGER001, HBOOT = 1.44.0000
- trying to install rom from http://forum.xda-developers.com/showthread.php?t=2531235
If you have S-OFF, you have probably saved your bum
Have you tried flashing a full RUU yet? You will need to find a RUU with a CID of ROGER001
It is also *possible* that you could change your CID to 1111111.
Let me see what I can find for you.
---------------------
Quick search didn't turn up anything for the ROGER001, have you ever changed CID? I would change it to the brightstar one and flash that...
---------------------
Here we go!
http://forum.xda-developers.com/showthread.php?t=2636103
Read the guide for flashing RUU's and you should be good to go!
Change your CID to BS_US001 and run the RUU listed here: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
There is no RUU for Rogers/Bell/Telus.
Thanks
Thank you guys. Changing my CID and flashing with the brightstar RUU fixed my cellular signal issues. You guys are the best.
The RUU has made my phone close to stock. I am back to HTC sense software and I was able to do an OTA update. The only thing I still have is S-OFF. Also, upgraded my HBOOT to 1.56.
What I would like to know, is it possible to make my phone seem like the GPE version HTC One and get OTA updates from Google and have no HTC sense software. My dream is to be able to pick any hardware and run vanilla android, and receive the updates right away. Please let me know if there is a way.
Once again thanks for the help you guys saved a phone.
I am having a ***** of a time here...
I have a Bell M7, I decided to convert to a GPE. I did it no problems. Now i'm selling it and I need to unlock the sim. I don't have the cable needed to do it with the USB drive. I need to convert this back to Bell. My biggest issue is there is no RUU for Bell.
Can I flash the Rogers RUU onto the phone then do the nandroid backup recovery with twrp to Bell.
I have the unlock code for the phone, but it tells me it's invalid. I think my SID is set to the GPE and not the Bell CID.
Anyone else run into this problem with going back to Bell stock?
Hboot is 1.54
CID is GOOGL01
Iz3man said:
I am having a ***** of a time here...
I have a Bell M7, I decided to convert to a GPE. I did it no problems. Now i'm selling it and I need to unlock the sim. I don't have the cable needed to do it with the USB drive. I need to convert this back to Bell. My biggest issue is there is no RUU for Bell.
Can I flash the Rogers RUU onto the phone then do the nandroid backup recovery with twrp to Bell.
I have the unlock code for the phone, but it tells me it's invalid. I think my SID is set to the GPE and not the Bell CID.
Anyone else run into this problem with going back to Bell stock?
Hboot is 1.54
CID is GOOGL01
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2207874 there's a cwm backup for bell
Iz3man said:
I am having a ***** of a time here...
I have a Bell M7, I decided to convert to a GPE. I did it no problems. Now i'm selling it and I need to unlock the sim. I don't have the cable needed to do it with the USB drive. I need to convert this back to Bell. My biggest issue is there is no RUU for Bell.
Can I flash the Rogers RUU onto the phone then do the nandroid backup recovery with twrp to Bell.
I have the unlock code for the phone, but it tells me it's invalid. I think my SID is set to the GPE and not the Bell CID.
Anyone else run into this problem with going back to Bell stock?
Hboot is 1.54
CID is GOOGL01
Click to expand...
Click to collapse
liam_davenport said:
http://forum.xda-developers.com/showthread.php?t=2207874 there's a cwm backup for bell
Click to expand...
Click to collapse
Theirs never been a Bell RUU ..where is your backup before converting to GPE? Also if you relock the bootloader with that CID their a chance your phone will be toast and you'll never be able to unlock it again.
You need to be Very careful the steps you take right now.
While your s-off revert to the stock MID/CID
Then flash your backup ( or the one posted above)
Don't lock the bootloader or s-on
Iz3man said:
I am having a ***** of a time here...
I have a Bell M7, I decided to convert to a GPE. I did it no problems. Now i'm selling it and I need to unlock the sim. I don't have the cable needed to do it with the USB drive. I need to convert this back to Bell. My biggest issue is there is no RUU for Bell.
Can I flash the Rogers RUU onto the phone then do the nandroid backup recovery with twrp to Bell.
I have the unlock code for the phone, but it tells me it's invalid. I think my SID is set to the GPE and not the Bell CID.
Anyone else run into this problem with going back to Bell stock?
Hboot is 1.54
CID is GOOGL01
Click to expand...
Click to collapse
I agree with clsA, you need to change your CID & MID. Then flash a nandroid backup if you have one or get one from crushalot's site. There is a TWRP backup for 3.23.666.1 which is newer. I would also leave it S-OFF.
majmoz said:
I agree with clsA, you need to change your CID & MID. Then flash a nandroid backup if you have one or get one from crushalot's site. There is a TWRP backup for 3.23.666.1 which is newer. I would also leave it S-OFF.
Click to expand...
Click to collapse
I'll give her a try
So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
xXgOrAiZeXx said:
So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
Click to expand...
Click to collapse
first you can not use "fastboot flash zip" to flash odexed rom or any other roms, they must be flashed using a custom recovery. Only firmware pacakge and ruu can be flashed this way.
I also see that your version main is 1.10.605.10 which is for verizon phones MID: PN0731000 (yours is PN0713000) and cid VZW__001 (yours is T-MOB010). It looks like you have flashed a verizon firmware on your t-mobile phone which is not a good thing.... Dont know what you have previously done to this phone but it looks like you are trying to hard brick it
Dont understand neither why you are trying to flash the 6.09.401.5 odexed rom that doesnt match your phone info...
Here are the ruu for your phone (PN0713000 and T-MOB010):
http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
http://www.htc1guru.com/dld/ruu-zip...157-04_release_336982_signed_2_decrypted-zip/
use one of them and see if your phone can recover (I hope that flashing the wrong firmware did not bricked it)
@alray Thanks for much for the info! Can't believe I was trying to flash the wrong ruu's :/. I will download the ones you provided and report back in few hours when I get home and hopefully my phone can still be saved.