I am trying to restore my T-Mobile One back to stock so I can send it back and exchange it for an S4... yet for some reason, every time I flash the stock ROMs, the touch screen dies. It works it in TWRP no matter what and it works in Android Revolution HD...
I *HAD* used the 1.54 firmware package but I used the 1.44 package...
I tried running the at&t RUU and it crashes as soon as it gets to the bootloader (I'm S-OFF and SuperCID so this makes no sense). I never modified my MID... I'm completely lost and this thing is supposed to go in the mail tomorrow. Can anyone help me? :/
Who would have thought... Where Windows 7 crashed on the at&t RUU as soon as it hit bootloader, Windows 8 which I despise so much is flashing the at&t RUU right now which should fix whatever I jacked up and enable me to flash TWRP through fastboot and the stock T-Mobile ROM and kernel. I hope. *fingers crossed*
Okay so it worked. Now I can remove SuperCID, flash the stock recovery, and remove S-OFF... Its going to show unlocked though but that shouldn't matter for a hardware issue.
I have had a Tmo HTC One since the day they came out. I rooted it, S-Off'd, Super CID, updated firmware and was running ARHD. Well the microphone stopped workng after a small drop and I had to have the phone replaced via Asurion insurance. I tried the warranty route, but I could not get the phone back to 100% stock and did not want to get screwed sending back an unlocked phone.
I just got my insurance supplied phone (I updated to the the 4.3 OTA from Tmo first thing) and being the glutton for punishment, I want to at least root it again and would love to run ARHD 30.x. In case of another warranty situation, I would like to make a backup of the phone in its stock state (recovery, ROM, etc...) and burn it to a DVD and put it away for safe keeping. Is this even possible? I cannot begin tell you how long I spent trying to get my original phone back to stock. I tried every tool, ROM and RUU and no luck. My understanding was because I updated the firmware and cold not go back down to a lower firmware and then I somehow relocked the bootloader and S-On'd and really screwed thing up.
The old phone is gone and is in the past, so whatever I did wrong doesn't matter. I just do not want to do it again this time around and anything I can do to create a safety net for the future, I will gladly do. My phone is completly stock running the Tmo 4.3 with 3.24 firmware.
What are my options?
fastboot boot recovery.img
But it stopped working after hboot 1.44, I dunno if it works on 1.55.
Otherwise you'll need to flash the recovery and find a stock recovery from eleswhere.
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 .
Greetings,
Long story but all well known, I tried to make my phone a developers edition, I tried RUU's could never get them to install but once via fastboot, I don't even remember which ruu's I tried but it's driving me insane, phone is S-OFF and unlocked, CID is super CID and MID is sprint's like I THINK it originally was, the restore went throughbut when I start the phone ir reboots when trying to go through the initial setup after it complains about an app crashing.
Model is m8_whl, it all started because I could not get the phone to update to marshmallow through OTA. At one point I flashed the firmware and I believe that it the issue but I have no clue as to what firmware should I be using.
Help please?