Camera becomes purple !!! - HTC Butterfly S

Anyone has the similar issue???. (Compare with the right one, SG note II).
I use other camera App (eg line camera) also has this problem. Especially during low light source. Even during daylight photography, there is some purple on the edges
IS it an hardware issue ?? Will this issue solve by update to 4.3 ??

patkylie said:
Anyone has the similar issue???. (Compare with the right one, SG note II).
I use other camera App (eg line camera) also has this problem. Especially during low light source. Even during daylight photography, there is some purple on the edges
IS it an hardware issue ?? Will this issue solve by update to 4.3 ??
Click to expand...
Click to collapse
Your are the first person here with that issue but if u jus bought it I suggest sending it back
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

Thx
in fact it is my wife's phone who brought July last year. The purple issue is not new actually. It happened since she brought it.
I am going to bring back to HTC but my phone is unlocked and rooted. So I am looking for ways to lock it back and unroot. Unfortunately there is too little info in here XDA forum. Can u help ?
Sent from my Nexus 5 using xda app-developers app

Hv to s off first
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

patkylie said:
Thx
in fact it is my wife's phone who brought July last year. The purple issue is not new actually. It happened since she brought it.
I am going to bring back to HTC but my phone is unlocked and rooted. So I am looking for ways to lock it back and unroot. Unfortunately there is too little info in here XDA forum. Can u help ?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I guess you'll have to do it the hard way. I think the following should work:
S-OFF your phone if it's not already
download a stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2422783
flash the ROM (this undoes root and any mods in /system)
reboot into recovery, adb shell, reset the "tampered" flag and lock the device according to these instructions: http://forum.xda-developers.com/showthread.php?t=2540434
download the latest firmware.zip from http://forum.xda-developers.com/showthread.php?t=2422783, rename it to PO68IMG.zip
copy PO68IMG.zip to the external SD card
reboot into bootloader – this should flash the original firmware, including the stock recovery
factory reset
At this point the phone should be as stock as possible.

koniiiik said:
I guess you'll have to do it the hard way. I think the following should work:
S-OFF your phone if it's not already
download a stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2422783
flash the ROM (this undoes root and any mods in /system)
reboot into recovery, adb shell, reset the "tampered" flag and lock the device according to these instructions: http://forum.xda-developers.com/showthread.php?t=2540434
download the latest firmware.zip from http://forum.xda-developers.com/showthread.php?t=2422783, rename it to PO68IMG.zip
copy PO68IMG.zip to the external SD card
reboot into bootloader – this should flash the original firmware, including the stock recovery
factory reset
At this point the phone should be as stock as possible.
Click to expand...
Click to collapse
Amazing guide. Can someone do a guide for a night out and going home to the wife?

Really thanks !and can you guide me how to s_off ?
And will it show "relock" rather than "locked" after all done ?
Finally my phone is actually 901s (LTE version), the rom is ok for it ?
Thanks
Sent from my Nexus 5 using xda app-developers app

patkylie said:
Really thanks !and can you guide me how to s_off ?
And will it show "relock" rather than "locked" after all done ?
Finally my phone is actually 901s (LTE version), the rom is ok for it ?
Thanks
Click to expand...
Click to collapse
To S-OFF, use rumrunner. They provide detailed enough instructions.
I don't actually know what exactly the bootloader is going to show after following this procedure, as I haven't tried to follow it. But my guess is that if you reset the "tampered" flag, it should display "locked" rather than "relock". Don't take my word for this, though.
And finally, yes, the ROM and firmware is based on my 901S, so yeah, it should definitely work on yours. Actually, I haven't seen dumps from the 901E around here. I'd love to get my hands on those as well someday, but I have no idea how and I don't really have the time to try and figure it out…

Ok thanks a lot. I will try that .
Sent from my Nexus 5 using xda app-developers app

koniiiik said:
To S-OFF, use rumrunner. They provide detailed enough instructions.
I don't actually know what exactly the bootloader is going to show after following this procedure, as I haven't tried to follow it. But my guess is that if you reset the "tampered" flag, it should display "locked" rather than "relock". Don't take my word for this, though.
And finally, yes, the ROM and firmware is based on my 901S, so yeah, it should definitely work on yours. Actually, I haven't seen dumps from the 901E around here. I'd love to get my hands on those as well someday, but I have no idea how and I don't really have the time to try and figure it out…
Click to expand...
Click to collapse
I have 901e stock Rom and 4.3 ota
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

daorderdillon said:
I have 901e stock Rom and 4.3 ota
Click to expand...
Click to collapse
Could you, please, upload it somewhere so I can package that version as well?

Sounds like a bad camera like the HTC One, google htc one purple haze focus blurry and see if its the same as urs, if so u will have to get a replacement, haolened to me w my HTC One

ultra pixel cameras
It's evident that in a huge batch of HTC One that the camera has a purplish/pinkish/reddish tint. This was identified by HTC as a 'software problem' and was supposed to be rectified in the 4.3 update for the HTC One. But the update did not resolve the issue, and thus it was established as a whole that it was a hardware issue. HTC has declined to comment further, and if you bring in your device (while being in warranty), you'll get a replacement or a free fix. I have this problem, and a distant acquaintance of mine has this problem too. However, my girlfriend doesn't have this issue. The three of us use the BS.
I am personally gonna send it in for repair before the warranty expires. Sad that the UltraPixel module has this problem. ):

I'm also having the same problem, but i think it's really my fault tho :silly: My camera was working perfectly fine, until I installed a nexus 4 camera 4.2 apk for photoshpere. The camera didn't turn purple yet, until I installed the 4.3 apk and deleted the old gallery using titanium backup, and THAT'S when the camera turns purple. Not just the stock camera but all apps that uses the camera including the HTC camera Is there anyway to restore this without flashing a new rom? Backing up my music and pictures would be quite painful

hmm, I started noticing it today under extremely low light. It's not so much a tint through the whole image but rather, a wavy pattern like purple clouds in the sky... My phone was a bit warm from playing games but not hot, and I decided to take some lowlight video after (and HDR video). I don't think the problem was there in low light pictures a few days ago though.
For me, HDR video ALWAYS has purple tint in low light and I supposed this was normal as I think HDR video was designed for daylight rather than lowlight. I've used it before but it might be that using it at low light damages the camera sensor?

koniiiik said:
I guess you'll have to do it the hard way. I think the following should work:
S-OFF your phone if it's not already
download a stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2422783
flash the ROM (this undoes root and any mods in /system)
reboot into recovery, adb shell, reset the "tampered" flag and lock the device according to these instructions: http://forum.xda-developers.com/showthread.php?t=2540434
download the latest firmware.zip from http://forum.xda-developers.com/showthread.php?t=2422783, rename it to PO68IMG.zip
copy PO68IMG.zip to the external SD card
reboot into bootloader – this should flash the original firmware, including the stock recovery
factory reset
At this point the phone should be as stock as possible.
Click to expand...
Click to collapse
Your method Works !! Thank you very much! Sorry for the long time since my wife FINALLY AGREED to repair the phone recently ~:angel:
but I have a question: after I restore all the stuff (s-on, locked, no "tampered" flag ), I try an Offical OTA update from the phone (i.e. settings --> software update) and it shows "Tampered" immediately after reboot into Hboot and not allow me to go on. I have to do the whole thing again to get S-off --> reset tampered flag + locked the bootloader, s-on) and avoid Offical OTA update from the phone ~~~
And there is few tricks during "restoration work":
1) If the phone is already Android 4.3 (that means you already get the lastest offical update), then rumrunner will not work, as the Hboot is also upgraded to 1.55 from 1.54.
However, using "firewater" in Hboot 1.55 is OK.
- I am not quite familar with ADB command. I realized that I can execute ADB command when the phone is ON, USB connected with USB debugging ON. no need to boot into recovery or fastboot etc (I spent quite a lot of time to figure it out !)
- Just copy the "firewater" file into your adb command folder and execute the script , then your phone reboot several times, and will get s-off
- be sure to grant the SU request automatically so that your won't miss the SU requests during the process
2) When you update the latest firmware, be sure you are flashing the lastest Offical ROM also.
I've flash the old rom (probably 1.23.708.3 OTA) and the lastest firmware here, I got bootloop.
And I tried to flash 2.21.708.1 CL288207 (should be the lastest OTA update) and the lastest firmware and everything is OK
3) After all the instruction, the phone is locked, no tampered flag but there is one more thing left: to get the phone from S-off to S-on
Boot into bootloader --> fastboot. type the command "fastboot oem writesecureflag 3" and you will get S-on again.
Be sure this is the last step or you will have to s-off again which takes a lot of time ~~~
[/B]
After all the steps, I sent the phone to HTC and they did not say anything about "void warranty" or "your phone software is modified", so I think once your phone is S-on, no tampered flag, locked bootloader, your warranty is still OK~
I will go pick up the phone today. HTC staff said they have replaced the camera hardware, hope the purple issue will be solved !!

Purple
I think it is definitely a hardware issue similar to the HTC One. Hardware warranty is the way to go.

patkylie said:
Your method Works !! Thank you very much! Sorry for the long time since my wife FINALLY AGREED to repair the phone recently ~:angel:
but I have a question: after I restore all the stuff (s-on, locked, no "tampered" flag ), I try an Offical OTA update from the phone (i.e. settings --> software update) and it shows "Tampered" immediately after reboot into Hboot and not allow me to go on. I have to do the whole thing again to get S-off --> reset tampered flag + locked the bootloader, s-on) and avoid Offical OTA update from the phone ~~~
And there is few tricks during "restoration work":
1) If the phone is already Android 4.3 (that means you already get the lastest offical update), then rumrunner will not work, as the Hboot is also upgraded to 1.55 from 1.54.
However, using "firewater" in Hboot 1.55 is OK.
- I am not quite familar with ADB command. I realized that I can execute ADB command when the phone is ON, USB connected with USB debugging ON. no need to boot into recovery or fastboot etc (I spent quite a lot of time to figure it out !)
- Just copy the "firewater" file into your adb command folder and execute the script , then your phone reboot several times, and will get s-off
- be sure to grant the SU request automatically so that your won't miss the SU requests during the process
2) When you update the latest firmware, be sure you are flashing the lastest Offical ROM also.
I've flash the old rom (probably 1.23.708.3 OTA) and the lastest firmware here, I got bootloop.
And I tried to flash 2.21.708.1 CL288207 (should be the lastest OTA update) and the lastest firmware and everything is OK
3) After all the instruction, the phone is locked, no tampered flag but there is one more thing left: to get the phone from S-off to S-on
Boot into bootloader --> fastboot. type the command "fastboot oem writesecureflag 3" and you will get S-on again.
Be sure this is the last step or you will have to s-off again which takes a lot of time ~~~
[/B]
After all the steps, I sent the phone to HTC and they did not say anything about "void warranty" or "your phone software is modified", so I think once your phone is S-on, no tampered flag, locked bootloader, your warranty is still OK~
I will go pick up the phone today. HTC staff said they have replaced the camera hardware, hope the purple issue will be solved !!
Click to expand...
Click to collapse
Hi, is it your phone return back to you since you have been sent to HTC. WHat's the status of your purple tint? Recently I found my BS also have this kind of issue. I bought it since last year September.
Thanks,

dioooi said:
Hi, is it your phone return back to you since you have been sent to HTC. WHat's the status of your purple tint? Recently I found my BS also have this kind of issue. I bought it since last year September.
Thanks,
Click to expand...
Click to collapse
Everything went fine All Tint is gone!!! HTC say nothing about my phone being tampered or else. They said they replace the camera unit of the phone .

I so much

Related

[Q] Restoring Rogers HTC One M7 to Factory without RUU ?

Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
WARNING: i'm the second owner of the phone. For warranty I would have had to send the phone to HTC. I suspect the HTC warranty won't apply to me anyhow. I suggest that in this situation, people just get the phone fixed on warranty if they have that option
First Steps:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ? (SEE UPDATE BELOW)
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ? (SEE UPDATE BELOW)
Thanks in advance !
same issue
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
LRail said:
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
So far:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ?
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ?
Q3) If I eventually decide to install the Developer Edition firmware.. will the phone be effectively be a Dev phone ? (OTA updates... factory recovery/locked bootloader... no ID issues in the future..)
Thanks in advance !
P.S. For pure curiousity.... Am I correct in believing that revone can't clear the "tamper" flag and lock the bootloader with the custom recovery ?
Click to expand...
Click to collapse
double post
omgkush said:
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
Click to expand...
Click to collapse
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
LRail said:
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Click to expand...
Click to collapse
Tampered will come back the second you flash a recovery. Best to stay S-OFF
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
ysl00 said:
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
Click to expand...
Click to collapse
Thanks for the heads up. If I get a bunch of free time I may just test that after doing a new full backup.
Not sure about the Rogers 4.3 OTA.
I'm running currently the phone with Developer Edition ROM+CID and can confirm that it's 4.3 OTA updates hboot to 1.55.
After the update my phone is still s-off.
I have previously rolled back to an older hboot via a firmware flash.
Since the phone is still S-OFF, I assume I can do that again if needed.
EddyOS said:
Tampered will come back the second you flash a recovery. Best to stay S-OFF
Click to expand...
Click to collapse
Thanks For the reply Eddy.
Recovery flashing sets the tampered flag even if it's a factory recovery from an OTA being flashed ?
I agree on the S-OFF normally.
This was a test to see if I could get it back to full stock for warranty if needed, and S-OFF would not be acceptable in that case.
please help!
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
millarrjm said:
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
Click to expand...
Click to collapse
Esposition said:
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
Click to expand...
Click to collapse
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
re.
LRail said:
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I tried that. CWM version 6.+ doesn't save to the backup folder anymore. And won't read a restore I put in it either... Ie. The rogers off the bugzylawson site.
bklam said:
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
Click to expand...
Click to collapse
Hello bklam,
Sorry, I missed your question.
No. I used CWM only to restore the "Whampahoofus"' nandroid backup.
That backup is "almost" 100% stock. Unfortunately it contains a custom recovery and won't (in my experience) work for normal OTA updates.
To solve this I decided to extract the factory firmware from one of the old Rogers OTA ("unrar" will extact the files from the OTA), and flash that.
To flash it I used the quick instructions in the 1st post of this thread-->http://forum.xda-developers.com/showthread.php?t=2182823
(I believe there were more details instructions on firmware.zip flashing in another thread but I can't find it at the moment)
Note to other readers: There can be confusion about the word "firmware". Some people use it describe the Rom.
In this case, I'm referring to the hboot, boot and recovery images in a single special file called firmware.zip. I believe in some cases it can also include the radio software too.
If I ever get a chance to get this 100% tested and figured out, I'll post a step by step method.
At this point it's just a overview of what I tried, and looking for other members advice.
Unfortunately, as you can see from my posts, it didn't work 100% for me. It gave me the stock Rogers HTC One Rom/software with OTA updates, but the bootloader still had the tampered flag.
Check out ysl00's post above. He/She evidently had it working 100% without the tamper flag.
Not sure if Rogers has a 4.3 OTA yet, but that might fix the flag since it includes a firmware update along with the OS update.
Post back with your results !
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
figured it out.
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
millarrjm said:
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
Click to expand...
Click to collapse
Sorry about that. No I didn't see it until just now. I guess thats the problem with having 20 browser tabs open at once. hehe
millarrjm said:
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
Click to expand...
Click to collapse
Good to hear. I read your post. I thought..."Is he using a root file manager ?" then read your next post….
I was also going to suggest a guaranteed way to determine where the CWM backups are being stored on a phone.
This way it doesn't matter which version of CWM, which phone or if the back directory exists yet.
Simply create a test backup and see where it goes. Then copy the Nandroid backup that you want to restore, there.
I should mention that I'm currently running my phone as a Developer Edition (Brightstar) 4.3 with OTAs, S-OFF, and unlocked.
It's works perfectly. Only the Carrier ID (CID) needed to be changed. The MID is the same.
I assume that a brightstar RUU will work on it now, even if the phone was locked and S-ON.
I have a few more things I want to tweak on it, then I'll likely make a backup and try restore it to stock rogers again so that I can create a clear how-to.
What's interesting, is that the Developer Edition OS seems to be the same as the Rogers Edition OS (without the rogers apps which can be uninstalled).
The only reason I think it might be a better choice is that the Dev Edition should get OTA updates earlier than the Rogers Edition.
I tried the custom Viper Rom 2.6.x but couldn't get an LTE connection. I suspect that was due to APN settings, but I didn't confirm that.
Anyone got the Viper Rom fully working on a Roger HTC M7 ?
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Esposition said:
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Click to expand...
Click to collapse
The OTAs don't work with custom recovery. You need the factory recovery

[Q]Possible to revert to stock - HTC One Three UK

Hi There,
After just recently switching to Android I have been having great fun customising my phone in ways I could never with my iPhone.
I currently running the latest release of TWRP Recovery and Using the Android Revolution HD ROM.
While there is currently nothing wrong with my phone I was just wondering what my options are in terms of going as far back to stock as I can.
Being 1.54 I understand I will always have re-locked on my device until an exploit is found or if I fancied shelling out for a Java Card.
In the popular RUU, OTA, etc thread under the Nandroid section is a recovery which would be compatible with my CID.
M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x
If I was to flash CVM and then proceed to restore this back and then flash the included recovery.img to my device 1. Would it work in the first place and 2. Would I be able to remove the Tampered warning.
Tbh I'm not overly worried about the warrenty. Espically being in the UK and our law covering things like this. But none the less I like being able to go down the simple root (See what I did there ) if I have to return the device.
Many Thanks and sorry for the noob question.
Syther101
1. Yes it should work
2. No it won't
You might also run into issues as you have 4.2.2 FW and will end up with a 4.1.2 ROM which might lead to touchscreen problems
Thanks for the reply Eddy. Yeah I was afraid of the touchscreen issue. Will have to have a tinker around when I get time.
From what I have read I was under the impression when you put the stock recovery abd stock ROM back on the device abd relocked the bootloader the tampered message would go.
Guess not then. Best just hope I don't have to return the device or wait for a new s-off
Thanks again
Syther101
Sent from my HTC One using XDA Premium 4 mobile app

Need Help Restoring Google Play Edition to Stock (HBOOT 1.54 - 4.3 AOSP)

Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app

[Q] Help switching to stock recovery

I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Smerfurdt92 said:
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Click to expand...
Click to collapse
you have to flash a RUU
Boachti said:
you have to flash a RUU
Click to expand...
Click to collapse
Its a Tmobile phone is there one for tmobile?
and doesnt that require s-off?
well the ruu I tried wouldnt even run on my Laptop
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
NxNW said:
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you guys im looking further into it. Does the phone need to be rooted to flash a rom or just have the bootloader unlocked?
For kit Kat it needs to be s-OFF. Let's get that out of the way first.
And some s-OFF methods require a rooted ROM to work as I recall. So it's already getting complicated.
But a typical custom Rom doesn't *need* root, in fact after flashing you will discover it *gives* you root.
Going that route requires work and some reading. Then again, getting an RUU to run successfully does too.
Basically the situation you''re in is not horrible, but to go all the way forward (S-OFF Kit Kat with ability to do anything you want in the future) or all the way back (totally locked down stock system capable only of accepting OTA's ) will require work either way.
Sent from my HTC One using xda app-developers app
So basicaly it may be simpler if I...
1 s-off
2 download rom
2.5 put on phone memory
3 go to team win recovery
4 Click install and choose said rom?
is that the basics of it?
if I want the least amount of trouble?
Also I guess what makes this most confusing for me is the non stock recovery
and to use fire water for the s-off I need to remove htc sync from the phone?
I feel im doing more work and stressing than i should be?
Yes Im quite Noobish..
Pretty much yes.
There could be adventures along the way, but I think this outcome would position you well for the future.
The biggest question is how old is your HBOOT.
There is no S-OFF for 1.57 and existing exploits for 1.56 don't always work.
If you can get S-OFF, you can do anything, including a) destroying your phone by mistake; b) changing your mind later and going back to S-ON; and, my personal favorite, c) destroying your phone in the act of trying to go back to S-ON (due to modified/ damaged HBOOT partition).
If you can't get S-ON, well, see if you can get back to stock.
Occasionally you are truly stuck and can neither go forward nor backward.
Which in your case is not so bad. 4.3 works great. Honestly plenty of people here are trying to go *back* to 4.3 after trying 4.4.
With S-OFF you can always do that. S-ON, not so much..
Sent from my HTC One using xda app-developers app
Yeah.. now i have a pretty blue screen that once every 10 minutes or so will flash the google logo so yup bricked...
That would qualify as an "adventure". Still, it sounds like something less than "bricked".
See if you can enter HBOOT (hold down volume-down and power buttons for a few seconds or if you're in a boot loop , just hold down volume-down as phone is booting up).
If so, you can select fastboot and you should have the option to power down. That should give the battery a rest and give you time to think.
At some point you need to have the android tools fastboot and adb set up on your computer.
When you do, enter HBOOT, select fastboot (with phone plugged into computer via USB) and run the command fastboot getvar all.
Post the results here.
The first post of this thread doesn't really contain enough detail for others to help you otherwise.
Sent from my HTC One using xda app-developers app

[Q] Just want it back like i just got it...

I rooted my phone thinking it would benefit me, like it did on my EVO 3D, however i cannot have been more wrong. First off all the ROMS i tried (CM11, viper, insert coin,) had either a buzzing noise from the top speaker, or the WIFI didn't work. Second i cannot update the firmware using the OTA update. I download it then try to install and all that happens is it boots into TWRP. I just want to know if there is a way to get it back to normal like i just got the phone. I tried finding my Cid and doing the unlocker method, but i didn't find any Cid labeled spcs_004. Is there just an RUU i can run that will get my phone back on track with sprint? I have the Harmon Kardon model of the M8 BTW. Also i never updated my phone since i got it, so i'm on firmware no 1.54.xxx.xx (i don't know the rest of the numbers off hand).
Go to the thread in the link below. Download the 3.31.654.2 RUU to your computer. Connect your phone and computer via USB cable and boot your phone into Fastboot USB mode. Open up a command terminal with your ADB/Fastboot folder, then re-lock your bootloader using the command fastboot oem lock (unless you're S-off). Leave your phone and computer connected and from either Fastboot USB mode or while booted to the Android OS double-click the RUU to start the installer. Follow the prompts on your computer screen to install the RUU. For more info hit the second link in my sig and read the RUU section of that guide.
http://forum.xda-developers.com/showthread.php?t=2729173
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
D3TH5150 said:
Thank you. It worked and my phone is working like i just got it. Big thanks for the quick reply.
Click to expand...
Click to collapse
Anytime, glad to help :thumbup:
I had the same problem just got my hk m8 rooted it and flashed nocturnal night vision ... had problems with WiFi and the Rom booting up as well as recovery so I ran the 3.31.654.2 RUU and got it running again, problem is I can't get a good signal my calls drop after like 30 seconds all the time... any help would be greatly appreciated I'll donate too
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Oh my gosh. If this helps get me back....
I screwed up and tried to flash ARHD v32 without being s-off and I've been without my M8 for 24 hours. And freaking out for the last nine. I knew it couldn't be that difficult to get back to reality.
BOOM shaka lakka!
I was just getting ready to call Sprint and go into a repair facility with some crazy story about how this all happened.
Thank you!:good::good::good:
Time to do some serious reading before I attempt that again.
Original Sprint CID number?
Magnum_Enforcer said:
Anytime, glad to help :thumbup:
Click to expand...
Click to collapse
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
cboy1234 said:
Okay so I did originally mess up rooting and flashing my HTC One m8 sprint edition. Since that day I succesfully (After 8 hours of horrible things) got it back to factory reset with the exception of S-off and the super cid. The thing is I dont want the super Cid because i DO want the OTA Update. The problem is I was a noob and forgot to save the original sprint CID number. So long story short. Does anyone have the Sprint CID number. Unless the Super CID number gets OTA updates for Stock. PLease and Thanks
Click to expand...
Click to collapse
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I have SuperCID and still receive OTA notifications.
Update to reset stock htc one m8
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
cboy1234 said:
So after doing more research I found that the image that I grabbed for stock android came from a H/K Edition. In fact the phone identifies itself as the as the Harmon edition ( I got the RUU from here http://forum.xda-developers.com/showthread.php?t=2729173) I was curious as you said that you yourself got OTA updates. Aside from lollipop, which updates did you receive. I only ask because I have heard of phones bricking up after doing an update and then something going wrong because they tampered with their tech. I DO want lollipop, but if it means losing my phone, then it is obviously not worth it.
ALSO looking at that website, I have verified that I got the NON-H/K edition....I am at a loss, I can try flashing it again, but honestly, I hate even looking at fastboot or any bootloader for the time being. Push comes to shove I will go down the rabbit hole again, but I do not want to risk a brick like before.
SIDENOTE: Not sure if its significant, but after flashing that RUU, I lost the weather widget at the top of blinkfeed, It only shows something such as "HIGHLIGHTS" If you would like I can post screen shots.
I am sorry to be such a noob and/or burden, and if you can help i would very much appreciate that if not, could you please direct me to a place where I could figure it out. Possibly a link or a person.
PLEASE AND THANKS!!!
Click to expand...
Click to collapse
I don't actually install the OTA I flash the previous version stock rom and download the OTA, then pull it from my phone so the devs can use it to build roms and pull the firmware.
It's pretty hard to brick these devices unless you do something really crazy. As long as you can get to recovery or bootloader it's only soft bricked meaning it can be saved.
I would suggest changing your CID back to stock
Code:
fastboot oem writecid SPCS_001
Then run the latest RUU that will put you where you need to be to take the OTA when it comes.

Categories

Resources