CID: GLOBA001 RUU Needed please - One (M7) Q&A, Help & Troubleshooting

I need to return my phone to stock (S-ON, CID: GLOBA001) and i cant seem to be able to find the appropriate files. Any help would be greatly appreciated.

Nastradamus said:
I need to return my phone to stock (S-ON, CID: GLOBA001) and i cant seem to be able to find the appropriate files. Any help would be greatly appreciated.
Click to expand...
Click to collapse
There is no RUU for WIND, afaik. Sorry

alray said:
There is no RUU for WIND, afaik. Sorry
Click to expand...
Click to collapse
Is there somewhere i can maybe find a saved backup of stock ROM. Or do you know any other way i can get back to stock ROM with S-ON? Thanks for your help!

Nastradamus said:
Is there somewhere i can maybe find a saved backup of stock ROM. Or do you know any other way i can get back to stock ROM with S-ON? Thanks for your help!
Click to expand...
Click to collapse
Do you need to get back to stock for warranty purpose?
What is your firmware version? (fastboot getvar all) or (fastboot getvar version-main)

alray said:
Do you need to get back to stock for warranty purpose?
What is your firmware version? (fastboot getvar all) or (fastboot getvar version-main)
Click to expand...
Click to collapse
Yea I want to send my phone in under warranty due to a problem with the wifi where it doesnt work and just gets stuck on ON. From what ive read everyone who had this problem ended up sending in their phone and just got a replacement. I originally had this problem while I was in stock so I tried out a custom ROM to see if that would fix the problem.
After putting a custom ROM didnt fix the problem, to try get back to stock I used a guru reset file. The CID from the reset file didnt match my phone but I gave it a shot. So now my phone has stock rom with android 4.3. Then I wanted to get an OTA so everything else would go to stock like kernel (Im fairly new to rooting and stuff so that's what I understood would happen). But my phone wont accept an OTA, after downloading for a bit it basically says that some modifications have been made to the software so it cant get the OTA.
I cant get my getvarall until later when I get home but from the about menu in the phone it says that the softwarenumber is 3.22.661.1 (is that firmware version?). ill post my getvarall when I get home.
If there's a way that you know I can get back to stock, that would be awesome. Thanks alot for your help.

Nastradamus said:
Yea I want to send my phone in under warranty due to a problem with the wifi where it doesnt work and just gets stuck on ON. From what ive read everyone who had this problem ended up sending in their phone and just got a replacement. I originally had this problem while I was in stock so I tried out a custom ROM to see if that would fix the problem.
After putting a custom ROM didnt fix the problem, to try get back to stock I used a guru reset file. The CID from the reset file didnt match my phone but I gave it a shot. So now my phone has stock rom with android 4.3. Then I wanted to get an OTA so everything else would go to stock like kernel (Im fairly new to rooting and stuff so that's what I understood would happen). But my phone wont accept an OTA, after downloading for a bit it basically says that some modifications have been made to the software so it cant get the OTA.
I cant get my getvarall until later when I get home but from the about menu in the phone it says that the softwarenumber is 3.22.661.1 (is that firmware version?). ill post my getvarall when I get home.
If there's a way that you know I can get back to stock, that would be awesome. Thanks alot for your help.
Click to expand...
Click to collapse
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...

alray said:
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...
Click to expand...
Click to collapse
The problem started when I had stock kitkat and persisted when I tried a custom rom based off lollipop (MaximusHD) and jelly bean which I currently have from the telus gurureset file. Yea I messed up by rooting and flashing custom rom in hopes of fixing the problem. Now I just want to get back to stock with relocked bootloader and hope it gets through warranty.
Ill post getvarall later today when I get home. btw there are a couple things I should black out before posting that right? Could you tell me which ones?
Thanks

alray said:
3.22.661.1 is telus ROM. I need to know what is your firmware version (from the bootloader or from the getvar all) so we can check if there is anything available to restore your phone (most likely a Nandroid backup). Both your software version and firmware version must be the same.
For warranty to be valid. your phone must be 100% stock which mean stock rom and firmware, no tampered flag in the bootloader. bootloader status must be "locked" (not re-locked or unlocked). Removing the tampered flag and resetting the bootloader to "locked" require s-off. There is nothing available for WIND (no RUU, no nandroid backup (to confirm with your firmware version)). So flashing a custom rom before checking for these files was not a good idea. When the phone is under warranty, you should always send it for repair because troubleshooting it by flashing custom roms (and unlocking the bootloader) void the warranty, unless you can return your phone to 100% stock (files needed and s-off needed).
But sometime, ppl are lucky and HTC will repair the phone even if its not stock. If they think the custom software might have caused the wifi problem, then they will charge you for the repair. If its an hardware defect, then you might get it repaired at no cost, at HTC discretion.
For ota update, you can't use them atm because the software version (TELUS) doesn't match your firmware version and CID (WIND)
Btw, is your wifi problem only on lollipop? I had some problem too and it was caused by the power saver mode. Disabling it (or at least the wifi power saver option) solved my issue. Just in case...
Click to expand...
Click to collapse
My firmware version is 5.11.1500.8

Related

problem with returning to stock and RUUs

I purchased a One off a friend which he told me had been rooted. I wasn't too keen on the idea but after looking in here it seemed moderately straightforward to get it back to factory settings again (but for the 'tampered' dialogue in the bootloader)
It is a SIM free model from Phones 4U in the UK so I figured I need the Europe RUU. I relocked the bootloader through fast boot but whenever I try to run RUU it freezes my computer up at the flashing stage (having taken sometimes up to TEN MINUTES just to open the app). Assuming it to be my old laptop I went to use my mum's PC and the same thing happens there. I have gotten as far as It saying 'boot loader' version error after an hour of waiting. Does this mean there is no RUU to flash my phone back to stock? And why is the RUU weighing down my phone so much?
Help would be terribly appreciated.
Just an update here. I've unlocked the bootloader again and the original ROM is still present. It's Android Revolution HD.
The recovery is CWM v6.0.3.0
I really want to get back to stock again. Can someone please tell me what I'm doing wrong? The guide said to relock the bootloader then flash the RUU but that is what got me in this position. I have two firmware files for Europe, neither of which work (boot loader error or something).
Does this mean that I am screwed with respect to ever getting this on stock firmware? It looks like there is no UK specific stock RUU nor even any nandroid ones.
If someone can help here I'd be really grateful.
You need to check the firmware version on the device at present. There are no UK RUUs as UK falls under EU, any RUU which is x.xx 401.x applies. Having said that, chances are the lastest leaked RUU (1.28.401.7) will be old compared to your current version so it wouldn't work anyway

[Q] Back to scratch ! Help.

Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.
nlcautela said:
Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader. @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.
Click to expand...
Click to collapse
Nothing u can do to back to stock.also after several check,I just know that unlockbootloader just give our to HTC service to know we have unlock and warranty is void even you have relock unless u havent bad luck. u can try from mike stock to get os up to date back.maybe.
nlcautela said:
Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.
Click to expand...
Click to collapse
nouxxer said:
Nothing u can do to back to stock.also after several check,I just know that unlockbootloader just give our to HTC service to know we have unlock and warranty is void even you have relock unless u havent bad luck. u can try from mike stock to get os up to date back.maybe.
Click to expand...
Click to collapse
of course you can go back to stock with s-on and you'll most probably keep your warranty. read first before you answer please...
here is a guide with several options: http://forum.xda-developers.com/showthread.php?t=2265618
just go back to stock as much as possible for you and you're fine. flash stock rom, stock recovery and relock bootloader ("fastboot oem lock"). :good:
herwegan said:
of course you can go back to stock with s-on and you'll most probably keep your warranty. read first before you answer please...
here is a guide with several options: http://forum.xda-developers.com/showthread.php?t=2265618
just go back to stock as much as possible for you and you're fine. flash stock rom, stock recovery and relock bootloader ("fastboot oem lock"). :good:
Click to expand...
Click to collapse
Thank you so much, just followed your procedure and now I only have two more questions.
1 - If possible how do I remove the tampered flag ?
2 - Will I receive further updates automatically ? and from whom, HTC or my carrier ?
Thank you one more.
nlcautela said:
Thank you so much, just followed your procedure and now I only have two more questions.
1 - If possible how do I remove the tampered flag ?
2 - Will I receive further updates automatically ? and from whom, HTC or my carrier ?
Thank you one more.
Click to expand...
Click to collapse
no, to remove tampered flag you'd need s-off, but this should not matter even in case of warranty.
with everything reverted back to stock you'll be able to recieve official OTA updates from your region again

[Q] Phone misbehaving after stock RUU flash

I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?
LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help
Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .

Process com.htc.dialer isn't responding

Hi i was update software by wifi to 4.4.2 and after reboot is start display message "process com.htc.dialer isn't repsonding wait or close"
and phone was rebooting every 30-60 seconds. I was make s-off, unlock bootloader, custom recovery twrp etc. install custom rom HD revolution but is same problem is unknow imei now and no signal
Anybody know how to fix it ?
EDIT 1
I was see the baseband also is unknown but i donwland radio flash from recovery reboot and still same
The radio which i use match with the version from fastboot, any chance to solve this issue ??
Regards
Anybody know how to fix the phone ?? i was try different roms etc. but nothing
still baseband, imei unknow but from fastboot is show normal imei and baseband
Regards
blackangel82 said:
Anybody know how to fix the phone ?? i was try different roms etc. but nothing
still baseband, imei unknow but from fastboot is show normal imei and baseband
Regards
Click to expand...
Click to collapse
Yes, I had the same issue.
In TWRP, wipe all the partitions except the internal storage. Then flash the rom and choose wipe in Aroma.
Im sure you wouldn't have manually wiped the partitions. The Aroma for some reason doesn't do the job. Manually wipe it and the ROM will install properly
raghav kapur said:
Yes, I had the same issue.
In TWRP, wipe all the partitions except the internal storage. Then flash the rom and choose wipe in Aroma.
Im sure you wouldn't have manually wiped the partitions. The Aroma for some reason doesn't do the job. Manually wipe it and the ROM will install properly
Click to expand...
Click to collapse
Hi thanks for reply.
I was try wipe all partition use stock firmware etc.
Always same no imei and baseband the only one thing only on 4.4.2 show me message "Process com.htc.dialer isn't responding." and sometimes with some roms phone not rebooting stay online all time
Regards
I am having this, along with a litany of other issues as well.
Hi thanks for reply, how you fix this ?
I was book apoitment in HTC service care but phone is unlocked and s-off
I'm wondering the same thing -- I'm stuck. I'm not even S-Off so I can't use this guide, which you may be able to: http://forum.xda-developers.com/showthread.php?t=2541082
Hi I will try tomorrow this and post results
Thanks
I've got the exact same problem - guessing it's hardware related.
Except mine reboots after 30-60 seconds.
This is the second time its happened - sending back again to get repaired.
Now going on the mission of reverting to stock (again) Lucky i'm SOFF
Hi, i was try this return to stock tampered and relock from bootloader gone but all time phone rebooting (loop)
Put back to cid o2 uk try use ruu exe but all time give me error 158
I will send back the phone but i must flash o2 uk ruu first, second somebody try open the phone without success, scratches, dents around the edge
Regards
I'm having this same problem. I've wiped it several times and reloaded 2 different RUU's and Android Revolution. With Android Revolution I've stopped it from randomly restarting but I still get the process error and it doesn't show a Baseband or IMEI. When I used the getvar in cmd it shows my IMEI and everything looks good.. not sure if its a hardware problem or what. Any ideas and if I have to send it back can anyone direct me to a US T-Mobile stock RUU? I'm still new to this... just switched over from a Galaxy.
chickenburritos said:
I'm having this same problem. I've wiped it several times and reloaded 2 different RUU's and Android Revolution. With Android Revolution I've stopped it from randomly restarting but I still get the process error and it doesn't show a Baseband or IMEI. When I used the getvar in cmd it shows my IMEI and everything looks good.. not sure if its a hardware problem or what. Any ideas and if I have to send it back can anyone direct me to a US T-Mobile stock RUU? I'm still new to this... just switched over from a Galaxy.
Click to expand...
Click to collapse
Have a look here :
http://www.htc1guru.com/downloads/ruu-file-downloads/
I was relock remove all tampered and relock put back to my cid s-on try run the only one available ruu.exe
Code:
RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2
File Size: 1.6 GiB - Downloads: 376
MD5: 4961fdbbadba53c9640f3638f56faec1
and ruu give me error 158 all time
right now in flash i have :
RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
Click to expand...
Click to collapse
but cannot go back to my cid
Hi probably i due wrong but not have other way, because the o2 uk ruu is corrupt and is no ruu zip i deicide to change cid to HTC___01 and restore to 100% stock.
Today courier was pick up the parcel and now will waiting for HTC Service what's wrong with my phone hope can fix it under warranty.
Strange is in fastboot you can read all baseband imei etc. and when phone is on-line rebooting all time and imei baseband etc. is unknown
Regards
blackangel82 said:
Hi probably i due wrong but not have other way, because the o2 uk ruu is corrupt and is no ruu zip i deicide to change cid to HTC___01 and restore to 100% stock.
Today courier was pick up the parcel and now will waiting for HTC Service what's wrong with my phone hope can fix it under warranty.
Strange is in fastboot you can read all baseband imei etc. and when phone is on-line rebooting all time and imei baseband etc. is unknown
Regards
Click to expand...
Click to collapse
^^ hardware problem, not fixable via ruu or any other software method i've seen.
nkk71 said:
^^ hardware problem, not fixable via ruu or any other software method i've seen.
Click to expand...
Click to collapse
i was read riff box can repair imei etc. but it cost over 100 pounds
anyway i was send the phone to htc but with different cid with removed tampered and locked bootloader
Now i must just wait but with my luck this not be cover and i must pay for repair
Regards
Hi i was receive message from htc :
Dear Lukasz Lipinski
Our initial assessment of your device indicates that the repair work required is caused by damage that isn’t covered by warranty. Unfortunately, this means we must charge you for the repair.
We have prepared a quote for you which you can view, accept and pay for at
zam. 74H02404-02M, 74H02439-14M, 83H40000-20 Laser Etching,HTC,CATCHER,Silver,PN07100,M7#UL_B128L3720-C9#EMEA£33,95
zam. 51H10208-03M, Rigid-Flex Board ASSY,w/o_Regional_ID,USB board£5,28
Labor£22,00
Shipping£11,29
Tax£16,68
Please bill me for the full repair£89,20
If you decide not to complete this repair, your device will be returned to you following receipt of payment for the administration and shipping costs incurred. You may use the same link as above to arrange this.
Many thanks,
HTC Customer Care
Click to expand...
Click to collapse
Please follow the link, anybody know what means the parts ??
Was same problem! This post save my phone!
http://forum.xda-developers.com/showthread.php?t=2503646
+ Video https://www.youtube.com/watch?v=0WWNZpaQBh8
westua said:
Was same problem! This post save my phone!
http://forum.xda-developers.com/showthread.php?t=2503646
+ Video https://www.youtube.com/watch?v=0WWNZpaQBh8
Click to expand...
Click to collapse
Hi, sorry I didnt watch the youtube guide (yet again)... but just a quick question, the thread you posted:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
got your GSM (m7_u/ul) device back to life? or was it the other way around?
nkk71 said:
Hi, sorry I didnt watch the youtube guide (yet again)... but just a quick question, the thread you posted:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
got your GSM (m7_u/ul) device back to life? or was it the other way around?
Click to expand...
Click to collapse
I have sprint device, after downgrade, root it again and now it works grate using gsm. Viperone 5.8.0 + Elementalx 13.1
I was try downgrade, root, s-off etc. nothing works always same problem
I was send phone to htc it will be repaired but not cover by warranty
the cost is 89 pounds because htc must change rear cover which previous owner damage trying takes off screen
Regards

Returning Back to Stock With Previously Saved Backup

Hi Guys,
Im in a spot of bother and am hoping for some advice. I have an HTC One m7 and about two weeks ago its wifi started acting up where it would get stuck on turning on and not work. I searched this problem up and most people who had it ended up sending their phone in for warranty repair. I figured that i would try a custom rom and see if that fixed my problem. So i unlocked my bootloader, rooted and flashed a custom rom. The problem went away for a bit but now its back, so I want to revert back to completely stock so that i can send it under warranty claim.
Problem is that I cant find an RUU file for my phone(CID GLOBA001); network provider is WIND (operated by Globalive). However I did make a backup of my stock ROM using TWRP before flashing the custom one. So if i restore that backup, all i have to do is get stock recovery&lock bootloader and I should be good for sending it under warranty? Or will I have to separately get other stuff back to stock such as kernel. P.S my phone is S-On
I Just want to make sure before doing anything because I am pretty new to this stuff.
Any help would be greatly appreciated
Nastradamus said:
Hi Guys,
Im in a spot of bother and am hoping for some advice. I have an HTC One m7 and about two weeks ago its wifi started acting up where it would get stuck on turning on and not work. I searched this problem up and most people who had it ended up sending their phone in for warranty repair. I figured that i would try a custom rom and see if that fixed my problem. So i unlocked my bootloader, rooted and flashed a custom rom. The problem went away for a bit but now its back, so I want to revert back to completely stock so that i can send it under warranty claim.
Problem is that I cant find an RUU file for my phone(CID GLOBA001); network provider is WIND (operated by Globalive). However I did make a backup of my stock ROM using TWRP before flashing the custom one. So if i restore that backup, all i have to do is get stock recovery&lock bootloader and I should be good for sending it under warranty? Or will I have to separately get other stuff back to stock such as kernel. P.S my phone is S-On
I Just want to make sure before doing anything because I am pretty new to this stuff.
Any help would be greatly appreciated
Click to expand...
Click to collapse
depends if your going to chance it being relocked instead of locked, that requires s-off
clsA said:
depends if your going to chance it being relocked instead of locked, that requires s-off
Click to expand...
Click to collapse
Hey i appreciate the reply. So if i get soff and get locked, is it okay to have soff when sending it for waranty repair?
Nastradamus said:
Hey i appreciate the reply. So if i get soff and get locked, is it okay to have soff when sending it for waranty repair?
Click to expand...
Click to collapse
yes but depending on your hboot s-off could cost you $25
clsA said:
yes but depending on your hboot s-off could cost you $25
Click to expand...
Click to collapse
I have Hboot 1.57 i believe. Do you think I should get s-off or chance relocked? And besides that, so do i need to get stock kernel and stuff back as well or will restoring the backup of my stock rom do that automatically. Cause right now i have a custom kernel as well since it came with the custom rom which i installed. Once again, thanks for your help
Nastradamus said:
I have Hboot 1.57 i believe. Do you think I should get s-off or chance relocked? And besides that, so do i need to get stock kernel and stuff back as well or will restoring the backup of my stock rom do that automatically. Cause right now i have a custom kernel as well since it came with the custom rom which i installed. Once again, thanks for your help
Click to expand...
Click to collapse
I would send it with s-on / relocked / stock backup /stock recovery
are you just getting the camera fixed ? and are you sending it to your carrier or to HTC ?
clsA said:
I would send it with s-on / relocked / stock backup /stock recovery
are you just getting the camera fixed ? and are you sending it to your carrier or to HTC ?
Click to expand...
Click to collapse
The problem is with my wifi, so i just want to get that solved. From what ive read from other people who had the same problem as me, they all got replacement phones when using warranty claim since the problem wasnt fixable. I plan on just going to the carrier's store and getting it fixed/replaced through them since theyll lend me a temp phone while mines gone.
So even if i have a custom kernel, sending it in shouldnt be a problem?
Nastradamus said:
The problem is with my wifi, so i just want to get that solved. From what ive read from other people who had the same problem as me, they all got replacement phones when using warranty claim since the problem wasnt fixable. I plan on just going to the carrier's store and getting it fixed/replaced through them since theyll lend me a temp phone while mines gone.
So even if i have a custom kernel, sending it in shouldnt be a problem?
Click to expand...
Click to collapse
use you stock backup + stock recovery + relock the bootloader and take it in
clsA said:
use you stock backup + stock recovery + relock the bootloader and take it in
Click to expand...
Click to collapse
Perfect, Thanks. Just one last thing, for getting stock recovery do i have to be wary of compatibility with my device like with firmwares or is that not the case with stock recovery?
Nastradamus said:
Perfect, Thanks. Just one last thing, for getting stock recovery do i have to be wary of compatibility with my device like with firmwares or is that not the case with stock recovery?
Click to expand...
Click to collapse
you need the same version that matches your firmware
if you have 6.x firmware find a 6.x stock recovery for your phone

Categories

Resources