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
Ok, I've already got around to resetting my CID to the stock CID number (VODAP102)
I'm using this site for all the downloads http://www.htc1guru.com/downloads/ - sadly since Vodafone doesn't seem that popular there isn't any RUUs for it, there are however a Nandroid backup, OTA update and Guru-reset.
My phone is currently S-OFF and rooted and has all the lastest firmware e.t.c, and since I can't find a guide on how to go to stock without a RUU I thought I better ask first!
Also side note, when changing firmware using the command with cmd to check the version number is fine, but when the phone is booted and I got to about>software infomation, it still shows the old software number, is that normal?
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 .
Hey guys,
Trying to figure out how to unbrick it before just calling the Carrier to sort things out there. Long story short, updated to 6.0 (stock firmware) and was working fine. But once I restarted the phone later in the day, it just got stuck on the boot screen. Really sucked...
Tried factory reset in the bootloader, no luck. Also tried to use the RUU for the latest firmware available currently, but for obvious reasons it doesn't work.
Therefore at the very least if someone could point towards the RUU version 5.11.631.8 Rogers, that would be a good start.
Free to any suggestions too! Used to flash roms and stuff when I had the Xperia X10 and the HTC Incredible so just need a brushing up on this stuff.
Also BTW, the Hboot is 1.57 but its also S-ON (never bothered to unlock it)
I messed up this phone big time, and I accept all responsibility. However, I would just want to know if it can be salvaged in any way at all possible.
Here is what happened:
I bought the phone on ebay. It was rebooting just after booting up. I read somewhere it had to do with the radio. I flashed the radios for the version yet no improvement. When Lollipop RUU came out I used it to update and it stopped rebooting, but no radio. I flashed it to a CDMA network here, as I usually do, yet no service. I paid for Sunshine and unlocked bootloader. I installed CWM and flashed CM11. No radio as well. I now went into adventure mode: What if I changed CID and install a Verizon RUU, maybe it could help. I changed CID to 11111111 and tried flashing a Verizon M7 RUU. It failed and asked for Model ID compatibilty. I went further and changed Model ID to Verizon (PN0731000) from Sprint Model ID (PN0720000) and there the problem started. The RUU failed again and the phone got stuck in this mode (see attached pictures). Fastboot still works but I think there's a mixup in the CID/MID so it can't take any RUU.
Is this phone recoverable? If yes, how? I will be very happy to try anything, even if it means spending extra to get it done. I would want to fix this and learn from the process.
Thanks in advance.
ezeuba said:
I messed up this phone big time, and I accept all responsibility. However, I would just want to know if it can be salvaged in any way at all possible.
Here is what happened:
I bought the phone on ebay. It was rebooting just after booting up. I read somewhere it had to do with the radio. I flashed the radios for the version yet no improvement. When Lollipop RUU came out I used it to update and it stopped rebooting, but no radio. I flashed it to a CDMA network here, as I usually do, yet no service. I paid for Sunshine and unlocked bootloader. I installed CWM and flashed CM11. No radio as well. I now went into adventure mode: What if I changed CID and install a Verizon RUU, maybe it could help. I changed CID to 11111111 and tried flashing a Verizon M7 RUU. It failed and asked for Model ID compatibilty. I went further and changed Model ID to Verizon (PN0731000) from Sprint Model ID (PN0720000) and there the problem started. The RUU failed again and the phone got stuck in this mode (see attached pictures). Fastboot still works but I think there's a mixup in the CID/MID so it can't take any RUU.
Is this phone recoverable? If yes, how? I will be very happy to try anything, even if it means spending extra to get it done. I would want to fix this and learn from the process.
Thanks in advance.
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2490792
Problem solved. I had to try so many things, but the good thing is that this phone (once you're S-OFF and can get into fastboot) is virtually unbrickable. At last everything works now, even the GSM unlock. I will try and outline the steps I went through in case someone someday needs it.
Of course no way to install Verizon ruu some hardware differences have been found