Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Yes HTC has a RUU (Rom Update Utility) You posted in the AT&T forums so I'm going to assume you need the AT&T RUU
You can download it directly from HTC Here
The RUU requires s-off or Relocked bootloader
you relock it with this command
fastboot oem lock
fastboot reboot-bootloader
I've tried that before the ruh fails BC the phone shows no operating system. I've tried several different ones. The one thing that I see in relation to all the ruu threads all say you should see a os version in the current field and in dont. Unless there's some other order of operations Im not aware of when trying to use them.
Sent from my GT-N7105 using XDA Free mobile app
I've solved this without an RUU. I will post a "SOLVED" thread in the development page.
Sorry for the delay folks
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Sorry for the sluggish delay, due to some scheduling conflicts and other hurdles came into play but nevertheless Im posting my solved post now. head over to the ATT HTC ONE ANDROID DEVELOPMENT FORUM TO FIND THE POST LABELED "SOLVED"
Related
I havent really messed around with modding any HTC phones before and I'm doing this as a favor for my brother before he leaves for the navy, so forgive my ignorance
The phone is un-modded (stock) The phone is stuck in a boot loop. I've tried doing a factory reset via recovery with no results. I have visited the ROM list in the dev section, but I'm afraid I'm a little lost.
Is there a stock(most recent) ROM I can get and install, and is there a thread that will help me get that done.
Any help would be appreiciated
Sorry to tell you, but there isn't a ROM on here that's going to do you any good at all. The reason why is the bootloader on that phone is locked. You'll notice when you enter the bootloader up in the top right it says S-ON. That must say S-OFF to flash another ROM. You're only fix is going to be what's called an RUU. An RUU will replace the radio, bootloader, and ROM. It's important to know what version you're currently running, as trying to flash an RUU that's older will cause problems you REALLY don't want to have. That information should also be found on the bootloader screen. The following are links to RUUs for the Thunderbolt. http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
http://www.themikmik.com/forums/viewforum.php?f=296
It's possible none on the xda link will work. That depends upon how current the firmware is. I can virtually guarantee you that that phone has firmware older than the RUUs at themikmik.com. Any more questions, like how to flash it, just hit me up or ask here.
And if I'm mistaken on any of this, please, somebody, set me straight.
I appriciate the advice. Im off for the next two days, and I do all this at work. I was unsure because my ATRIX and xperia were easy to change the rom on regardless of the bootloader. I will definatly hit you up if I need help
Sent from my MB860 using XDA Premium App
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
Trying to install cyanogen mod.
First I tried to s-off before unlocking the bootloader (which I later learned was a mistake).
I tried everything except facepalm in the following order: (moonshine, rumrunner, firewater).
For firewater I was able to root/temp root via Minimal ADB and Fastboot as well as Weaksauce.apk.
None of those worked, but thankfully none of them bricked the device, however there has been some problems since then.
When I realized I should have been trying to unlock the bootloader this whole time, I tried SuperCID.apk from the soure.zip found in the development sticky thread.
That also failed.
Details about the phone:
Motherboard replaced ~3 months ago.
HTC sent the phone back to me running software number 1.15.605.4 710RD (Android 4.1.1)
While attempting root/s-off/unlock bootloader the SIM was installed but the phone was not activated and was in airplane mode.
I do not have OEM cable however ADB recognizes the device being attached so I don't think that is an issue.
Problems that have developed:
Since tinkering around the boot times have extended dramatically with some funny behavior at initial startup.
The battery is draining noticeably quicker.
I factory reset the phone and booting has gotten a little smoother, no battery improvement.
Aside from those 2 problems the phone functions perfectly.
I'd really like to be rid of the stock rom and all of its bloat apps, so if there is another way to get a CM ROM I'd be damn happy.
Also, any information on what I may have funked up when trying moonshine/rumrunner/firewater would be greatly appreciated.
Did you ever figure this out? I have been unable to unlock my bootloader too.
Yes!
gabezermeno said:
Did you ever figure this out? I have been unable to unlock my bootloader too.
Click to expand...
Click to collapse
I was able to figure it out after HOURS or even days of confusion.
In my case the problem I was having, was using the incorrect unlock/s-off method for the my corresponding firmware.
I upgraded via Verizon updates from firmware 1.XX to 2.XX until I eventually got 3.6 (it took multiple updates to get there). Once I had 3.6 I used the RUMRUNNER method to unlock and s-off (it was quite easy once it I had adb and fastboot commands all figured out).
Good luck.
I just bought a new at&t HTC One (M8) and I'd like to have a fresh stock backup in case of return/warranty problems. I'd like to make this myself so I can ensure that I'll be able to put the exact software that came with my phone back if need be. Also I'd just like to know how to do this in general. What I've found via search has been for rooted phones or different brands. Is it possible to use ADB or any other tool to do this? I guess I'm confused because I see posts for flashing back to stock. How do devs get these stock roms? If someone could point me to a good guide/tutorial it would be much appreciated.
Not without a rooted device or an unsecure [email protected] backup...there is an ruu posted for the 1.58.502.1, thats as close to being a backup without altering the phone in anyway
As long as you are a current account holder, AT&T does not give a crap what software is on your phone, bootloader unlocked, even a custom ROM installed in regards to warranty service based on many reports on XDA.
If you are still wondering about returning to stock, as mentioned in the above, your version (AT&T) if fortunate enough to have a 1.58 RUU. The ROM Update Utility is a useful means of installing a full stock image (ROM, radio, recovery, etc.) via connection to a PC.
But it can still be determined the bootloader is unlocked, no matter what you do to the phone to return it to stock. Your IMEI is tracked by HTCDev.com when you unlock the bootloader. But again, as long as you go through AT&T for warranty service (highly recommended for this reason) they don't care if the phone is modded.
I believe the stock ROMs you mention are system dumps done after bootloader unlock.
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available. I seen a guide and tutorial from theunlckr, but it's from mid 2014.
I'm looking for a complete guide from start to end that will put this phone back to stock. This would be my first time and I don't know jack about what to do when it comes to this stuff. I'm very computer savvy so it shouldn't be a issue.
The info is following when I boot into recovery:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Software Status : Modified
Unlocked
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OPENDSP-v47.2.2-00564-M8974_FO.1024
OS-4.28.502.1
eMMC-boot 2048MB
4/20/15
There is also a Team Win application or recovery when I choose to do a factory reset.
Please if someone can help, I need to do this soon.
rlockwich said:
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available.
Click to expand...
Click to collapse
You want the Lollipop (Android 5.0.2) AT&T RUU (software number 4.28) which is linked on my Index thread at the top of the General AT&T M8 forum section: http://forum.xda-developers.com/showthread.php?t=2751432
Relock the bootloader (command: fastboot oem lock) then just run the RUU (Windows executable).
rlockwich said:
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
Click to expand...
Click to collapse
What "completely" stock means is a bit complicated (and may vary depending on the person). You can relock the bootloader and run the RUU. Everything will be stock, except that the phone will say RELOCKED in bootloader instead of UNLOCKED (which is the factory condition).
The only way to make it say LOCKED is to s-off by sunshine ($25) then change the flag to LOCKED. Then go back to s-on. But IMO, its not worthwhile to spend money to sell/trade a phone; and not worth the money, time and effort for something that is very minor.
Functionally, there is no difference between RELOCKED and LOCKED. The only reason anyone would care, is if they want to make a warranty claim with HTC. In that case, they may deny any claim anyway, since there is already a record of the bootloader being unlocked via HTCDev.com (tracked by the phone's IMEI). Not even sure if the warranty (1 year from purchase) would be valid, anyway for a device that has changed hands 2 times.
I would recommend you ask the buy/trade partner if RELOCKED bootloader is okay. Otherwise, find someone else to trade with.
rlockwich said:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Click to expand...
Click to collapse
This, and TWRP recovery will be gone once you RUU.
RUU will re-image the entire phone to stock factory (Lollipop) condition. So it will be stock ROM, stock recovery, no root, etc.
You should also remove your SD card (if one is inserted), then go into phone settings and wipe all storage, to make sure the internal storage/virtual SD is wiped of your personal data.
Will this make him be able to do OTA updates for when 5.1 comes?
rlockwich said:
Will this make him be able to do OTA updates for when 5.1 comes?
Click to expand...
Click to collapse
Yes. The only requirements for OTA are stock ROM and stock recovery, which post-RUU state satisfies both.
Note that OTA updates for the AT&T version are only available when connected to AT&T's network. So if the buyer is asking if he will get OTAs, and he happens to be using another carrier, the answer is NO. And in that case, the RUU for the next update is his best option.
It was a success! Thank you for taking the time to help me out. I really appreciate everything you've done!
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
rlockwich said:
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
Click to expand...
Click to collapse
Can never remember for certain; but I think RUU just wipes user data, and normally leaves internal storage intact. Not just files used for root, but personal files, too. So you will want to make sure internal storage is wiped.
Therefore, I do recommend going to Backup & Reset in Settings, pick Reset phone in order to make sure internal storage is wiped.