Related
INTRODUCTION
It seems that a lot of Canadians are having this problem, so I decided to make a guide on how to bypass it. For my guide on flashing RUUs on the Canadian IS, click here.
THE PROBLEM
People with a Canadian Incredible S are continually getting the "Model ID Incorrect" error. This error occurs because the Canadian IS has the model ID PG3212000 while it seems every other IS has the ID PG3213000, which is blocking us from installing it... But luckily there is a way to fix this error.
THE SOLUTION
NOTE: It seems many people are having problems. After reflashing my phone and S-OFF'ing it again I had the same problem. Turns out ENG S-OFF is needed for this! Find out how to install it here: http://forum.xda-developers.com/showthread.php?t=1070348
To install a PG3213000(Any non-Canadian Incredible S) radio on a PG3212000(a Canadian Incredible S) follow these instructions:
1. go to: http://forum.xda-developers.com/showpost.php?p=12870734&postcount=1 and download whichever radio matches your rom...
2. extract the file you just downloaded and open up the file called: "android-info.txt" in WORDPAD...
3. In the text file change the first line saying "modelid: PG3213000" to "modelid: PG3212000" and go File -> Save.
4. Rezip the file and make sure you call it: "PG32IMG.zip". Copy it the root of your SD card.
5. Reboot your phone in bootloader and let it install... DONE!
NOTE: It seems many people are having problems. After reflashing my phone and S-OFF'ing it again I had the same problem. Turns out ENG S-OFF is needed for this! Find out how to install it here: http://forum.xda-developers.com/showthread.php?t=1070348
which one do you find works best with the bell is?
It all depends on what ROM you're using... You always want to use the radio recommended for the ROM... if it's a RUU, the radio is already in it.
I'm on the Virtuous Unity 1.26.0 ROM and oddly enough there isn't a reccomended ROM.
Also is this way any different than extracting the radio image and pushing it through fastboot?
Both have the same results, but this doesn't require andriod sdk, any work in command prompt, or ENG S-OFF... And I would recommend the 20.2804.30.085AU_3805.04.03.22_M radio
I was wondering how to do this since I need to update my radio to install CM7. Thanks so much for the tutorial!!
Hey can you use this guide when trying to flash a ruu? It never works when trying to flash a RUU because of Model ID incorrect... I am stuck in bootloader because of that...
ClaudiuJer said:
Hey can you use this guide when trying to flash a ruu? It never works when trying to flash a RUU because of Model ID incorrect... I am stuck in bootloader because of that...
Click to expand...
Click to collapse
I have tried that before and it did not seem to work... All it did was install the HBOOT and radio from the RUU and then it rebooted my phone...So essentially all it did was revert my phone back to S-ON... I will keep playing around with RUUs and will release a guide if/when I figure out how to flash them.
kattara said:
I was wondering how to do this since I need to update my radio to install CM7. Thanks so much for the tutorial!!
Click to expand...
Click to collapse
Glad I helped you out
charch said:
I have tried that before and it did not seem to work... All it did was install the HBOOT and radio from the RUU and then it rebooted my phone...So essentially all it did was revert my phone back to S-ON... I will keep playing around with RUUs and will release a guide if/when I figure out how to flash them.
Glad I helped you out
Click to expand...
Click to collapse
Yea I am stuck in bootloader because I was running Gingerbread and when I try to go back to my stock RUU I can't because it is Froyo and I receive "Main Version is Older" error...
ClaudiuJer said:
Yea I am stuck in bootloader because I was running Gingerbread and when I try to go back to my stock RUU I can't because it is Froyo and I receive "Main Version is Older" error...
Click to expand...
Click to collapse
Reflash a Gingerbread radio... Unfortunately it is currently impossible to downgrade your radio from Gingerbread to Froyo... It will put you into a never ending boot up loop.
Wait... Are you saying you successfully flashed a GB RUU? How?
charch said:
Reflash a Gingerbread radio... Unfortunately it is currently impossible to downgrade your radio from Gingerbread to Froyo... It will put you into a never ending boot up loop.
Wait... Are you saying you successfully flashed a GB RUU? How?
Click to expand...
Click to collapse
No it doesn't work... It was only when I was S-Off that I installed Android Revolution rom and that upgraded me to gingerbread... Well after that I accidently did a hard reset which removed my S-off and I am now stuck in bootloader with ***Security Warning***. The only way to fix it is by flashing a stock RUU but since this is Bell IncS only Sasktel rom works and I cannot flash that because I get the error "Main Version is Older" error.
Noob here. What's RUU?
ClaudiuJer said:
No it doesn't work... It was only when I was S-Off that I installed Android Revolution rom and that upgraded me to gingerbread... Well after that I accidently did a hard reset which removed my S-off and I am now stuck in bootloader with ***Security Warning***. The only way to fix it is by flashing a stock RUU but since this is Bell IncS only Sasktel rom works and I cannot flash that because I get the error "Main Version is Older" error.
Click to expand...
Click to collapse
I don't know what you can do to fix that, unfortunately... Post a question in the general forum and hope that someone can help you out with more information...
Edit: :O maybe that's why the RUU didn't complete the installation and rebooted my phone! The radio was newer then the version in the Optus RUU?!?! Omg that might have been my problem...
kattara said:
Noob here. What's RUU?
Click to expand...
Click to collapse
RUU is an acronym for ROM Update Utility... It is an official update for the phone which makes it as though it was new and seem like it was never tampered with(no root, no custom recovery, not custom HBOOT, returns you to S-ON, etc).
I believe this has been posted elsewhere, but if you are unable to flash your radio AND you are already ENG S-OFF the following works perfectly.
Download: http://www.megaupload.com/?d=WIWVHF7O
Make sure HTC Sync is installed
Extract ZIP to a folder and from that folder run the following:
1. Connect your phone into a PC, and make sure that USB Debugging is enabled
2. Type: "adb reboot bootloader"
3. Once your phone is in bootloader (white screen with text), type "fastboot flash radio radio.img"
4. When the flashing completes, type "fastboot reboot"
This works on any version of the IS, including the Canadian one. I included the recommended radio, however any radio can be used by replacing the radio.img file.
Other radios here: http://forum.xda-developers.com/showpost.php?p=14834003&postcount=1
you_eeeeeediot said:
I believe this has been posted elsewhere, but if you are unable to flash your radio AND you are already ENG S-OFF the following works perfectly.
Download: http://www.megaupload.com/?d=WIWVHF7O
Make sure HTC Sync is installed
Extract ZIP to a folder and from that folder run the following:
1. Connect your phone into a PC, and make sure that USB Debugging is enabled
2. Type: "adb reboot bootloader"
3. Once your phone is in bootloader (white screen with text), type "fastboot flash radio radio.img"
4. When the flashing completes, type "fastboot reboot"
This works on any version of the IS, including the Canadian one. I included the recommended radio, however any radio can be used by replacing the radio.img file.
Other radios here: http://forum.xda-developers.com/showpost.php?p=14834003&postcount=1
Click to expand...
Click to collapse
Yes, I know, but this makes it so that ENG S-OFF is not required as it is a little bit overkill... Plus, I used this as my basis in an attempt to installing RUUs on the Canadian version of the IS, since I was told it is not possible unless I XTC clip it... I proved those people wrong.
It doesn't seem to work for me.
I edited the android-info.txt file, re-zipped and placed the file onto the sd card. When I reboot into hboot, it says "Loading PG32IMG.zip" then "Parsing" then nothing else happens.
EDIT: Never mind, I got it to work using the other method.
charch said:
I don't know what you can do to fix that, unfortunately... Post a question in the general forum and hope that someone can help you out with
RUU is an acronym for ROM Update Utility... It is an official update for the phone which makes it as though it was new and seem like it was never tampered with(no root, no custom recovery, not custom HBOOT, returns you to S-ON, etc).
Click to expand...
Click to collapse
Ahh, I see! Thanks for the explanation!!
biomech91 said:
It doesn't seem to work for me.
I edited the android-info.txt file, re-zipped and placed the file onto the sd card. When I reboot into hboot, it says "Loading PG32IMG.zip" then "Parsing" then nothing else happens.
EDIT: Never mind, I got it to work using the other method.
Click to expand...
Click to collapse
Hmm... It didn't work for me either. I still get the same error...
kattara said:
Hmm... It didn't work for me either. I still get the same error...
Click to expand...
Click to collapse
Yes, it seems ENG S-OFF is needed for this work. I updated the orginal post with the information.
charch said:
Yes, it seems ENG S-OFF is needed for this work. I updated the orginal post with the information.
Click to expand...
Click to collapse
Ah, ok! I will try it!
Alright, because there is constant stupidity regarding the bootloader security state for HTC devices. I feel that I can clarify and help remove some myths and misconceptions.
Let's start with the most important one:
What is S-off?
S-off is us turning off the security flag stored in the NV RAM of our device. This allows us to flash unsigned files (zips and images) to our device. The difference is stated below of why you need a zip vs an image.
S-off is not root either. Root is just a binary stored in /system and just doesnt get removed if the device has s-off. S-off just means integrity of file system / partitions aren't checked on the device. So this means the two are exclusive of each other from a user standpoint.
HTC IS JUST GOING TO TURN S-ON AND RUIN IT FOR EVERYBODY!
No, they aren't. For a few good reasons, one of which is their own engineers have s-off to begin with.
The @secuflag (S-on/S-off) is there to verify hboots and other various image files on the device to begin with. When we have s-off on a newer device but idiot user decides to turn s-on for whatever reason and we have a modified hboot? The device will brick because you broke its chain of trust. It thought you were friends but you slept with it's girlfriend or whatever. Now if HTC were to suddenly turn s-on, this would break chains of trust for those who used something like Moonshine with a patched hboot. It was their OTA that caused it. They are then held liable for it and they have to fix it under warranty. You know how much that costs them? Imagine giving 1000's of people new phones because you singlehandedly broke them all. Good job dude.
Not only that, they cant turn S-on by just updating images on the device. It's stored in the NV-RAM. They would need an entirely different method than just flashing through recovery.
Next point is:
S-off means you can flash whatever you want using fastboot flash.
Now because s-off processes before gave us patched hboots, we didnt know any better. This is all wrong. fastboot flash barely works on newer phones unless dev unlocked. Now that not all s-off's give a patched hboot it's good to know the following. The only way to install something with a locked bootloader but s-off, is to use flash zip. This means that you dont just "fastboot flash recovery" or boot.img. You need to create a zip with android-info.txt and whatever files your flashing. With the lock placed on devices, unless you htc dev unlock or flash a modified hboot, it wont allow you to flash because the dev unlock is a different part than what flashes the zips.
More info about patched / eng hboots:
Now that we've seen what we lose without a patched hboot, what does it add exactly? Well, a patched or engineering hboot allows you to fastboot flash pretty much every partition on the device with an unsigned image directly (such as fastboot flash hboot hboot.img or fastboot flash splash1 splash1.img) without giving you a not allowed or command error. The reason these are useful is because it saves time. I really dont want to always have to build a zip so I always use patched hboots. They also give you access to more commands as well which I can't remember off the top of my head. These are all commands mainly used by HTC engineers and software testers.
Final point that I can think of (may add more):
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Nice write-up I added it to the FAQ's thread Q9 Thanks
Very nice thread, thanks
+1 on that green progress bar, when I removed the red writing on the splash screen I saw the progress bar not don't but in command prompt it said finished so I said whatever and just rebooted
Sent from my HTC One using Tapatalk 2
Reminds me of a certain thread I wrote about a year ago
S-OFF explained - by a Developer
Didn't even know that existed.
Sent from my hidden jewel
Question, let's say I have s-off and flash the superuser app and all the required busybox files... Can I use root required apps like titanium backup and wireless tether?
I only ask because I've been hesitatent to root. I just don't want to Dev unlock via HTC and officially void my warranty. The sealed in battery has me extremely paranoid as its generally the first thing I've had to replace with previous HTC devices.
This leads me to the following question, if the response to the first was no... Is there a way to use root apps without using the HTC Dev tool
Please note: I'm not a developer and this was not clear to me in the write up.
You don't need s-off to root.
You do need to root to use apps that require root access.
budeone said:
You don't need s-off to root.
You do need to root to use apps that require root access.
Click to expand...
Click to collapse
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
bnapy said:
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
Click to expand...
Click to collapse
I found this link, may answer your question.
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Indirect said:
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Click to expand...
Click to collapse
I don't know about "tits on a snake," but many progress bars I've seen are both uninteresting and pointless. They do generally serve their purpose of keeping impatient/inexperienced users from hammering away at things they don't understand and inadvertently breaking them.
tws101 said:
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
tws101 said:
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
PillowMetal said:
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
Click to expand...
Click to collapse
Another misconception about S-OFF is that you need a "valid android-info.txt" when flashing from fastboot. When you're S-OFF, the bootloader completely disregards that file. All you need is to make a zip with whatever you want flashed, and then add any android-info.txt file in there. The default one that I include in the plugin template for my Bootloader Customizer is actually completely empty and it works fine as well. As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
That's good to know, and thanks for the bootloader customizer, I have been using it for years, as well as your "rebooter" which is very convenient. Glad to see you in the One forums!
regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
PillowMetal said:
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
Click to expand...
Click to collapse
Ah, you don't have a bootloader that allows fastboot flashing? That must be why. If you were flashing straight from the hboot, you don't need it. Didn't realize you guys had to use RUU mode.
regaw_leinad said:
Didn't realize you guys had to use RUU mode.
Click to expand...
Click to collapse
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
PillowMetal said:
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
Click to expand...
Click to collapse
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
regaw_leinad said:
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
Click to expand...
Click to collapse
Ah, never thought of trying different formatting, there are different allocation unit sizes I could use... thanks! I will definitely make a guide if I get this resolved because it is driving me crazy, so I'm sure there are others too.
I just took the sprint update, and I am soft but locked. Originally used revone but can't unlock after update.
I am still soff what are my options. All I want to do is reinstall su.
Anyone?
htc dev
This is why we NEVER take an OTA HTC makes it harder and harder for us to modify our devices with every update
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
tws101 said:
So basically on the HTC one soff does nothing if your also locked? Nothing I can do except HTC dev?
Click to expand...
Click to collapse
HTC Dev unlock will allow you to flash a recovery, root, and install a custom rom if you so choose. Realize however that most custom roms are based on 1.29 and will likely have camera and wifi issues with the new firmware.
If you're S-OFF, you can RUU back to 1.29 and be a-okay, provided that the Sprint OTA does nothing beneficial that you need. If you're not S-OFF, it is possible to S-OFF via revone 0.21 and ADB. Most will tell you that it cannot be done but I managed it with little effort. Just don't try using it with a terminal app on the device, it probably won't work. ADB shell + revone will S-OFF someone locked on 1.31.x.
Personal experience, the 1.31 firmware and update made my cell reception weak as hell and wifi unusable at times even when I had full signal. It apparently activated HD voice, but I haven't noticed. That's what prompted me to S-OFF 1.31 and downgrade with a RUU.
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
tws101 said:
If I ruu back will I have to clear the phones memory? I assume yes.
Is there anyway to just install superuser?
Is there anyway to unlock?
I am soff. Locked on the new firmware.
Click to expand...
Click to collapse
Long as you're S-OFF, you should be able to flash a 1.29 RUU (like I did) and downgrade. If you dev unlock, you can flash a recovery from fastboot and install supersu from there. There's a supersu flashable zip here:http://download.chainfire.eu/315/
So flash this http://forum.xda-developers.com/showthread.php?t=2250904
Then revone will grant me unlock again then I can use twrp to flash su again?
Correct?
I flashed that RUU and still had S-OFF. Even if you, for whatever reason, lose S-OFF - just HTC Dev unlock. You can flash a recovery, install supersu, and be about your day without ever touching S-OFF.
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
tws101 said:
I have not done anything yet but since I am soff can't I flash a zip from fastboot?
Meaning just flash superuser even though I am locked?
If this is possible does anyone have a link to superuser with an androidinfo.txt with it so I can flash it in fastboot?
Click to expand...
Click to collapse
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
sshede said:
Download a recovery,
fastboot flash recovery downloadedimage.img
Then download the supersu zip I linked in one of my last posts. Reboot into the recovery and flash the zip. Mission accomplished.
Even without S-Off, all of this can be done. Even custom roms can be flashed on the One with just HTC Dev unlock. I'm not sure what you mean by s-off but locked. Just make sure you're HTC dev unlocked or S-Off, follow the steps above, and all of your problems will go away.
Click to expand...
Click to collapse
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
My understanding is that with a locked bootloader, you're still going to be locked out of changing boot-time code (given that the entire purpose of a locked bootloader is to prevent modifications to onboard software that could compromise secure information), unless you're using a runtime exploit (which is generally for rooting only, and I don't know that there are any such exploits for the Sprint One).
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
krazyflipj said:
Not sure if this would work but if you used revone try unlock command in step 6 of OP http://forum.xda-developers.com/showthread.php?t=2314582
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
That was the very first thing I tried.
After updating via OTA i ran revone with -u and got segment fault. Based on the revone thread it will no longer work once you take that OTA. Everyone is getting the segment fault after OTA.
I figured with an update.zip and using fastboot flash update.zip If the update putting an Android-info.txt file might work. I know fastboot flash recovery rec.img fails.
tws101 said:
I am LOCKED with S-OFF
This command will not work: (Already tried it)
fastboot flash recovery downloadedimage.img
I want to avoid HTC DEV as it clears the phone.
It is my understanding I can use the fastboot flash command if I flash a zip with a android-info.txt file in it. According to the forums that should work since I am S-OFF. Instead of flashing a recovery I was thinking of just flashing SU that way but havn't found an SU pre-prepared to flash that way.
Click to expand...
Click to collapse
Okay, now I understand a bit better. Why not just take the 11 minutes required to back up whats on the phone, then HTC dev unlock?
Just to update everyone Indirect helped me solve this issue.
1. Create txt file named android-info.txt
Data in file 4 lines
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
2. Get recovery of your choice and rename it recovery.img
3. Zip files up into zip file name of zip does not matter
4. Run the following fastboot commands
fastboot oem rebootRUU
fastboot flash zip nameofzipfile.zip
fastboot reboot
You now have a recovery of your choice on a LOCKED S-OFF system and can re-flash superuser.
Thank to Indirect!!!
I have a customer who's unrooted HTC One is bootlooping after he did an update that he doesn't recall the name of. He doesn't have nor has he ever had root or a custom ROM. He is extremely keen to get his text messages from the phone, and I am wondering if there is a step by step process I could undertake to try and recover those ?
I can get to download mode and to another mode which offers factory reset etc..
Anyone able to help please?
networkn said:
I have a customer who's unrooted HTC One is bootlooping after he did an update that he doesn't recall the name of. He doesn't have nor has he ever had root or a custom ROM. He is extremely keen to get his text messages from the phone, and I am wondering if there is a step by step process I could undertake to try and recover those ?
I can get to download mode and to another mode which offers factory reset etc..
Click to expand...
Click to collapse
I won't be able to help, but maybe this COULD help:
1- are you still on hboot 1.44? that COULD give a glimmer of hope, as you could use revone to unlock without wiping
2a- if however you are on hboot 1.54+, then (to the best of my knowledge) you need to use HTCdev to unlock, and that WILL WIPE everything
2b- if you are on hboot 1.54+, you could use a Java Card to get S-Off, then downgrade to hboot 1.44 (NB: I do not know if a Java Card wipes anything!!!)
why hboot 1.44, because it allows for "fastboot boot <name of custom recovery>.img", where you would be able to use adb commands to pull the sms database (I think it's stored in "/data/data/com.android.providers.telephony/databases/") though you would still need to find a way to decode the sql db.
I use this: https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en to backup SMS messages to an xml file (doesnt work for MMS), but you need a functioning ROM for that.
nkk71 said:
I won't be able to help, but maybe this COULD help:
1- are you still on hboot 1.44? that COULD give a glimmer of hope, as you could use revone to unlock without wiping
2a- if however you are on hboot 1.54+, then (to the best of my knowledge) you need to use HTCdev to unlock, and that WILL WIPE everything
2b- if you are on hboot 1.54+, you could use a Java Card to get S-Off, then downgrade to hboot 1.44 (NB: I do not know if a Java Card wipes anything!!!)
why hboot 1.44, because it allows for "fastboot boot <name of custom recovery>.img", where you would be able to use adb commands to pull the sms database (I think it's stored in "/data/data/com.android.providers.telephony/databases/") though you would still need to find a way to decode the sql db.
I use this: https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en to backup SMS messages to an xml file (doesnt work for MMS), but you need a functioning ROM for that.
Click to expand...
Click to collapse
Thanks for your help, how do I determine what versions of whatever I have?
Hmm what is the best step by step guide I can follow to recover my device if it's bootlooping? I can get into download mode and recovery mode.
networkn said:
Thanks for your help, how do I determine what versions of whatever I have?
Click to expand...
Click to collapse
in bootloader: HBOOT-1.xx.xxxx
Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to). What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Anyone know whether these kinds of dependency exist, or whether HBOOT and the contents of other partitions are completely independent of one another and no crosschecking is performed? It seems to me that HBOOT 1.44 is the real sweet spot given the simplicity of revone and the ability to boot from an image that's not on the device itself.
Full disclosure: I'm running an M7_UL on Rogers (PN0712000 and CID ROGER001), S-OFF, bootloader unlocked, no root with currently stock 3.22.631.1 firmware and ROM.
Thanks folks,
Ian
dr_diem said:
Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to).
Click to expand...
Click to collapse
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Click to expand...
Click to collapse
Not 100% sure but I have downgraded to 1.44 many time and it did not caused any issue.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Click to expand...
Click to collapse
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.
Many thanks for the rapid and informative response alray!
alray said:
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
Click to expand...
Click to collapse
Really?! All the more annoying
alray said:
Not 100% sure but a downgraded to 1.44 many time and it did not cause any issue.
Click to expand...
Click to collapse
That's really promising - thanks!
alray said:
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
Click to expand...
Click to collapse
That's the mustard right there! I don't know if anyone knows the definitive answer on all this, but my gut tells me that (for GSM single-SIM handsets at least) the further down the software->firmware chain you go the more generic the code becomes. Your findings seem to support that theory.
alray said:
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.
Click to expand...
Click to collapse
Yeah, it's because I would like to back up my stock recovery before rooting, so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery. Again I don't know if stock recoveries are tied to a particular firmware or ROM release (any idea on that one?), but I'm trying to play safe!
In general I find there aren't too many Rogers images out there (HBOOT, firmware, OTA, RUU...) which makes the rooting dance that bit more tricky for us. I tried to grab the OTA file when I recently went stock to go 1.29.631.17 -> 3.22.631.1 but of course one needs to root in order to access /temp to go get the file and I didn't want to root before I took a vanilla backup - catch 22! I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me a whole load of trouble
Cheers,
Ian
dr_diem said:
Yeah, it's because I would like to back up my stock recovery before rooting
Click to expand...
Click to collapse
stock recovery can be extracted from the ota package in the firmware.zip file.
so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery.
Click to expand...
Click to collapse
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Again I don't know if stock recoveries are tied to a particular firmware or ROM release
Click to expand...
Click to collapse
yes, use the recovery that match the version of your phone firmware/software.
I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me
Click to expand...
Click to collapse
no sorry
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
but there is no 3.22.631.1 which is an old version btw...
---------- Post added at 03:45 PM ---------- Previous post was at 03:39 PM ----------
dr_diem said:
.
Click to expand...
Click to collapse
you might want to take a look at what I have done: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
look under "for reference, here is how the recovery was pulled:"
alray said:
stock recovery can be extracted from the ota package in the firmware.zip file.
Click to expand...
Click to collapse
Yeah it is unfortunate that I failed to obtain that
alray said:
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Click to expand...
Click to collapse
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Huge thanks for the edit and pointer to how to dd without root!
alray said:
yes, use the recovery that match the version of your phone firmware/software.
Click to expand...
Click to collapse
Understood, thanks.
alray said:
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Yes I've combed my way through every repository I can find, but like I say ROGER_001 is a poorly-served CID I guess if I was really pushed I could go SuperCID and use the TELUS one I see there!
alray said:
but there is no 3.22.631.1 which is an old version btw...
Click to expand...
Click to collapse
Yeah the reason I'm so keen to have a complete path to downgrade to stock 4.3 is because I'm not convinced I ever want to go beyond 4.3. 4.4 makes Google Search become the shell, which is a line I'm not sure I want to cross :laugh:
Ian
dr_diem said:
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Click to expand...
Click to collapse
Yes you'll need either root or to downgrade hboot to 1.44, boot a custom recovery (fastboot boot), use dd from the custom recovery shell to pull the stock recovery from mmcblk0p34 partition. look in my previous (edited) post. I have posted a link explaining how to do it.
That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian
dr_diem said:
That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian
Click to expand...
Click to collapse
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...
alray said:
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...
Click to expand...
Click to collapse
Hah, yeah, touch wood I've never yet bricked any device using dd, but I'm clear how powerful/dangerous it is as commands go
Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian
dr_diem said:
Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian
Click to expand...
Click to collapse
glad to know it worked fine! happy flashing