Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:
reservin said:
Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:
Click to expand...
Click to collapse
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.
kibmikey1 said:
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.
Click to expand...
Click to collapse
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?
reservin said:
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?
Click to expand...
Click to collapse
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.
kibmikey1 said:
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.
Click to expand...
Click to collapse
I successfully flashed Europe RUU with 1.44 hboot!
Now I am restoring nandroid 4.1.2 backup. I still need aussie 4.1.2 firmware.zip as well right?
You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app
paul_59 said:
You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yep. I need to visit service center next week.
Now i am not sure if OTA still can be applied on Australian rom + European firmware with locked bootloader and s-on..
Related
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Ardmanz said:
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Click to expand...
Click to collapse
Any ideas?
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
prodizo said:
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
Click to expand...
Click to collapse
Hey,
Yup this worked perfectly (almost). Reset your CID to your originally carriers before running the nandroid backup or it will be missing your carriers boot screen.
The only thing is the recovery seems to be missing. I'd expect the HTC recovery to load when selecting it from the bootloader but all I get is a red triangle. I obviously need to sort this before sending it back (Monday).
Any ideas?
I haven't s-on'd yet because I want to sort out recovery first. That should be pretty simple though.
I guess I just need a link to stock recovery.img.
Just tried and mine does same. I have stock recovery so thats fine.
Hope you get a nice new one:laugh:
Cheers
Stock recovery will display a red triangle..your all set
Sent from my HTC One using xda app-developers app
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Ardmanz said:
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Click to expand...
Click to collapse
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Grand_Goblin said:
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Click to expand...
Click to collapse
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Ardmanz said:
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Click to expand...
Click to collapse
matursuwun - Thank You so much! (in Javanese)
I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?
dingnangen said:
I updated firmware to 2.24.401(s-off),but now I have a camera issue,I want to go back to 1.29.708.16(I can't find this firmware) then turn to s-on for warranty,there isn't update to 4.2 in HK(where I bought the phone),so how can I downgrade firmware to 1.29,and can I change the firmware number by change "mainver" in android-info.txt ?
Click to expand...
Click to collapse
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860
crushalot said:
If you are returning your phone for service then you can run an RUU if your phone has one.
It will reset everything back to stock, even the firmware. Check here:
http://forum.xda-developers.com/showthread.php?p=39588860
Click to expand...
Click to collapse
can 2.24 firmware use 1.29 ruu?how to do it ?
dingnangen said:
can 2.24 firmware use 1.29 ruu?how to do it ?
Click to expand...
Click to collapse
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.
crushalot said:
If your s-off then a RUU can downgrade your firmware. (I did this on a phone I returned for service without issues) If you are still s-on I don't think it will.
You just download the RUU.exe and run it on your PC and it guides you through resetting everything on the phone.
Click to expand...
Click to collapse
thank you very much,i'll try it.if there aren't my ruus of region,I use other region ruu,can I get warranty?
That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497
crushalot said:
That depends on the carrier/vendor. If you don't have a RUU you could also run an RUU for another area (Since your S-off) to downgrade the firmware and then root it and use one of the posted stock nandroids to restore to your proper areas stock config. Then do the stuff to re-lock your bootloader. http://forum.xda-developers.com/showthread.php?p=43458497
Click to expand...
Click to collapse
I can back to stock rom,but firmware version can't change,because there aren't ruu of HongKong,any ideas to change firmware version?
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?
dingnangen said:
thank you ,downing ruu now . is there Hboots red warning by using ruu back to stock?
Click to expand...
Click to collapse
The red warning in hboot is from being unlocked. Once you have back to stock (especially recovery) then the red warning will be gone. For sure after re-locking.
crushalot said:
Since your S-off you can change your CID to use another RUU like this one:
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/
The RUU will set the device firmware back to stock. Then restore your stock ROM and you should be ok.
Also if you have it stock rom and setup now, you may just want to put S-on so that it says Locked and S-on on bootloader and your vendor will probably not care about the firmware version.
Click to expand...
Click to collapse
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.
dingnangen said:
how to backup my stock recovery,because I must flash custom recovery to restore my rom,then back to the stock recovery.
Click to expand...
Click to collapse
Sorry, I'm not sure I understand what you are asking here.
crushalot said:
Sorry, I'm not sure I understand what you are asking here.
Click to expand...
Click to collapse
how can I backup stock recovery?
because there are not ruu of HK,so I should use TWRP to restore nandroid backup from HK htc one. then back to stock recovery .
Yes you would TWRP to restore and then flash the stock recovery and relock.
Here is a post where I helped another and it has the stock recovery and instructions for flashing if needed.
http://forum.xda-developers.com/showpost.php?p=43625746&postcount=17
Just an FYI that this method will not downgrade the firmware, but just get you back to locked and a stock look, but with the newer firmware.
Let me know if you need something else.
Hello everyone
I updated my htc OTA to 4.2.2 then rooted and unlocked and installed 4.2.2 google edition, now I resored back to HTC 4.2.2 and I am selling my phone so I want to relock and and unroot, how can I do that?
elibi said:
Hello everyone
I updated my htc OTA to 4.2.2 then rooted and unlocked and installed 4.2.2 google edition, now I resored back to HTC 4.2.2 and I am selling my phone so I want to relock and and unroot, how can I do that?
Click to expand...
Click to collapse
Well i hope your S-Off so you flash a 4.1.2 RUU because there aren`t any 4.2.2 RUU`s available afaik atm. Or flash this 4.2.2 (odexed) rom http://forum.xda-developers.com/showthread.php?t=2224752 in recovery. After that flash the stock recovery.img ( also on the linked site) in fastboot and do fastboot erase cache. After that relock bootloader in fastboot: fastboot oem lock. Then at the end do a data factory reset. Look here also for going back to stock http://forum.xda-developers.com/showthread.php?t=2358738.
What is S-off? I have Superuser installed, I have another problem, I don't know what my old SUU was, it is updated to 2.24.401.2 CL211355 release-keys
I just checked and found S-On, am I stuck?
elibi said:
I just checked and found S-On, am I stuck?
Click to expand...
Click to collapse
What version is the Hboot?
If you have 1.44.00 go to revone and get S-Off, link to revone http://forum.xda-developers.com/showthread.php?t=2314582. Then you can flash almost any RUU. Or restore a nandroid backup, link http://forum.xda-developers.com/showthread.php?t=2207874
hi there,
I'm on stock rooted 4.2.1 with cwm recovery and trying to get the 4.2.2 ota.
It can't be updated cause I don't have the stock recovery.
I have seen failed recovery reboots cause of the wrong cid of the stock recovery, so i guess flashing the stock recovery is not an option?
My cid is HTC_E11, and for as far as i know there is not an RUU for this one.
Any suggestions? Thanks in advance:good:
shaggydiamond said:
hi there,
I'm on stock rooted 4.2.1 with cwm recovery and trying to get the 4.2.2 ota.
It can't be updated cause I don't have the stock recovery.
I have seen failed recovery reboots cause of the wrong cid of the stock recovery, so i guess flashing the stock recovery is not an option?
My cid is HTC_E11, and for as far as i know there is not an RUU for this one.
Any suggestions? Thanks in advance:good:
Click to expand...
Click to collapse
There is a nandroid backup for the HTC__E11 (Dutch) CID here http://bugsylawson.com/files/file/1864-m7-cwm-nandroid-backup-cid-htc-e11-12940112/ on this site http://forum.xda-developers.com/showthread.php?t=2207874. Why don`t you flash the 4.2.2 stock rom by Mike1986 which is easily rooted or another custom rom like Viper or Android Revolution. Make sure to get S-Off before you update to 4.2.2 in case of warranty you had to revert to full stock, link S-Off http://forum.xda-developers.com/showthread.php?t=2314582.
gee2012 said:
There is a nandroid backup for the HTC__E11 (Dutch) CID here http://bugsylawson.com/files/file/1864-m7-cwm-nandroid-backup-cid-htc-e11-12940112/ on this site http://forum.xda-developers.com/showthread.php?t=2207874. Why don`t you flash the 4.2.2 stock rom by Mike1986 which is easily rooted or another custom rom like Viper or Android Revolution. Make sure to get S-Off before you update to 4.2.2 in case of warranty you had to revert to full stock, link S-Off http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
So that nandroid is 4.2.2, and 4.2.2 can't be S-Off (yet)?
This gives me doubts whether or not I should update it. I want to be able to revert to 100% stock just in case i need to.
but hey look at this > (dutch article from tweakers.net) http://tweakers.net/nieuws/90336/htc-gaf-klanten-onterecht-geen-garantie-na-unlocken-bootloader.html
shaggydiamond said:
So that nandroid is 4.2.2, and 4.2.2 can't be S-Off (yet)?
This gives me doubts whether or not I should update it. I want to be able to revert to 100% stock just in case i need to.
but hey look at this > (dutch article from tweakers.net) http://tweakers.net/nieuws/90336/htc-gaf-klanten-onterecht-geen-garantie-na-unlocken-bootloader.html
Click to expand...
Click to collapse
If you do S-Off on 4.1.2 it will stay S-Off even after the update to 4.2.2. You will always be able to revert to 4.1.2 with a RUU.
Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
WorldIRC said:
Hi Guys,
I want to restore a TELUS Canada HTC One back to as stock as possible for warranty exchange purposes.
There is no RUU available for TELUS, but I do have a TWRP Nandroid backup. The device's HBOOT has been updated to 1.54, and the device is currently S-OFF / SuperCID via Revone and obviously unlocked bootloader with TWRP recovery. As well, the device is running the ARHD ROM.
What order / process do I need to follow to get this back to as stock-like as possible?
Click to expand...
Click to collapse
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
crushalot said:
-Manually flash back the stock 1.44 hboot (and any custom splash you may have flashed)
-Nandroid restore (make sure it includes recovery, if not manually flash the stock one)
- Set CID back to stock
- S-on with revone
- Relock bootloader
Let me know if you need help with any of the steps.
Click to expand...
Click to collapse
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
WorldIRC said:
Where would I get the stock 1.44 HBOOT and stock Recovery? I'm using the TELUS TWRP Recovery from here: http://forum.xda-developers.com/showthread.php?t=2207874
Click to expand...
Click to collapse
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
crushalot said:
The Nandroid should include the stock recovery.
The stock hboot can be downloaded here: http://d-h.st/qfc
It is from post 2 of sneakyghost's guide which has the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2316726
Let me know if you need anything else.
Click to expand...
Click to collapse
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
WorldIRC said:
Curious -- since making a Nandroid requires a custom recovery, how would that Nandroid contain the stock recovery?
Click to expand...
Click to collapse
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Awesome -- I'll be trying this once my replacement unit has arrived. I'll let you know how everything works out.
crushalot said:
A few different ways. First, once you have a custom recovery installed, the 2 main recovery's used (TWRP & CWM) have an option to backup the recovery.
Second, when a new user unlocks their bootloader, they can then use fastboot commands to boot the custom recovery but keep the stock recovery installed and then it can take a backup of it. Example would be:
fastboot boot customrecovery.img
Also possible via a few different other more complicated methods.
If the nandroid you download doesn't have the stock recovery (the few that I downloaded for parts all had the recoveries, so I assumed it was a requirement before they would post a backup) then just give a shout around here and I can find a link for you.
Click to expand...
Click to collapse
Not sure why I'm having so much difficulty with this.
I've restored the 1.44 HBOOT referenced above.
I've restored the stock TELUS ROM via TWRP referenced above.
I can boot into the phone, but I have no touch-screen response now. Also, that TWRP backup did not include the stock recovery and I'm not sure which one I should push.
Tried flashing: http://forum.xda-developers.com/showpost.php?p=41953560&postcount=32 and now I have a red triangle recovery.....
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
crushalot said:
OK, everything is normal. The red triangle means it is the stock recovery.
The touchscreen doesn't work because you must have updated your firmware. If you still have s-off then you can downgrade that back to stock before s-on and re-lock. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=2316726
Download and install the package he has for " Base 1.29 Firmware, original unmodified"
After that you should be stock and just need to s-on and re-lock the bootloader.
Click to expand...
Click to collapse
That site needs a "decryption key"?
WorldIRC said:
That site needs a "decryption key"?
Click to expand...
Click to collapse
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
crushalot said:
Not sure what thats about. I will look into it and try to host those files on my site. However for now, you only need the touchpad driver part of the firmware which can be downloaded from his thread without a key here:
https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
Click to expand...
Click to collapse
How am I flashing this?
WorldIRC said:
How am I flashing this?
Click to expand...
Click to collapse
Same way as the firmware zip's. You use the same guide from post 1.
crushalot said:
Same way as the firmware zip's. You use the same guide from post 1.
Click to expand...
Click to collapse
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
WorldIRC said:
Thought so, wasn't 100% sure
Anyways - that worked. I have control of my Touch Screen. I'll await your response on the rest of the firmware, at which point I'll finish everything up and send you some beer for your time
Click to expand...
Click to collapse
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Will give it a shot later today and let you know!
crushalot said:
Here you go bud. This is the stock firmware from 1.29.401.12. It has the stock radio and recovery(just in case).
https://dl.dropboxusercontent.com/u/36946918/1.29.401.12.zip
If you flash that, it should put everything back to complete stock in regards to the firmware.
Should be able to s-on and relock afterwards and should be no signs of mods.
Let me know if you need help finishing up.
Click to expand...
Click to collapse
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
WorldIRC said:
Well now I've done it. Reflashed the firmware, put my CID back to TELUS001. Went back to S-ON, locked BOOTLOADER.
Now I am showing TAMPERED / LOCKED.
I reunlocked the bootloader, and am now showing TAMPERED / UNLOCKED, with stock recovery. I put back on TWRP and it shows TAMPERED / UNLOCKED.
I tried re-running REVONE and I am unable to go back to S-OFF.
What the heck happened?
Click to expand...
Click to collapse
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
crushalot said:
Can you verify your hboot is back down to level 1.44?
If it is, we should be able to revone to s-off again, but we may need to try a few times.
Did you have tampered displayed before you went s-on?
It did display locked rather than relocked so that it good. However it must be picking something up as non original as that is what causes the tampered flag.
Click to expand...
Click to collapse
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
WorldIRC said:
Yes, I am on HBOOT 1.44 from April 2013.
Tampered was not present before (I had hidden it with Revone). Tampered came back only after I re-locked the bootloader (with the stock recovery via firmware file you provided to me).
I tried to go S-OFF but I keep getting error 2 or 6 when doing ./revone -P
Meanwhile no issues doing 2 other phones with Revone (fresh out of box).
Click to expand...
Click to collapse
I had one phone that gave me trouble with revone. I tried it like 20 times and nothing was working. Then I ran all the commands in a terminal window on the phone rather than adb shell and it worked. Can you try that?
There are also some other good tips in the revone thread, but I forget them all and will have to read it again.
It wouldn't have been the recovery as that for sure was the stock recovery. Did you download the stock nandroid or did you make it yourself?