Related
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
I took a long break from messing with my phone. I stopped right about the same time ICS came out. I never upgraded. Now that I have battery issues, it is time to refresh my ROM. I am also getting a new battery. I was looking into getting the stock rooted ROM for my phone (2.3.4 with Sense 3.0). I am finding more and more ICS ROMs so I think that is where I should go.
I am currently unlocked with HBOOT 1.83.0014 with CWM-based Recovery v5.5.0.4.
I found the SuperGuide and it walks through relocking and reflashing the stock ROM, but the linky for the RUUs doesn't have my Gingerbread ROM. Can I relock and flash the ICS ROM?
duckredbeard said:
I took a long break from messing with my phone. I stopped right about the same time ICS came out. I never upgraded. Now that I have battery issues, it is time to refresh my ROM. I am also getting a new battery. I was looking into getting the stock rooted ROM for my phone (2.3.4 with Sense 3.0). I am finding more and more ICS ROMs so I think that is where I should go.
I am currently unlocked with HBOOT 1.83.0014 with CWM-based Recovery v5.5.0.4.
I found the SuperGuide and it walks through relocking and reflashing the stock ROM, but the linky for the RUUs doesn't have my Gingerbread ROM. Can I relock and flash the ICS ROM?
Click to expand...
Click to collapse
Oh my there is still someone on gb....bro....UPGRADE you are missing out. And yes I think you could just relock and flash the ICS RUU
duckredbeard said:
I took a long break from messing with my phone. I stopped right about the same time ICS came out. I never upgraded. Now that I have battery issues, it is time to refresh my ROM. I am also getting a new battery. I was looking into getting the stock rooted ROM for my phone (2.3.4 with Sense 3.0). I am finding more and more ICS ROMs so I think that is where I should go.
I am currently unlocked with HBOOT 1.83.0014 with CWM-based Recovery v5.5.0.4.
I found the SuperGuide and it walks through relocking and reflashing the stock ROM, but the linky for the RUUs doesn't have my Gingerbread ROM. Can I relock and flash the ICS ROM?
Click to expand...
Click to collapse
You will need to update your recovery as well... CWM has issues on the vivid.. TWRP I suggest.
esloan said:
You will need to update your recovery as well... CWM has issues on the vivid.. TWRP I suggest.
Click to expand...
Click to collapse
Is Slapshot's SuperGuide (http://forum.xda-developers.com/showthread.php?t=1416836) all I need? Is it one stop shopping for my situation?
I am on AT&T and I see three of the RUUs on the link have "cingular"....if I am running GB and wanting to finish with ICS, which one should I get?
duckredbeard said:
Is Slapshot's SuperGuide (http://forum.xda-developers.com/showthread.php?t=1416836) all I need? Is it one stop shopping for my situation?
I am on AT&T and I see three of the RUUs on the link have "cingular"....if I am running GB and wanting to finish with ICS, which one should I get?
Click to expand...
Click to collapse
You may need to read the ICS - WARNING!!! READ BEFORE UPDATING!!! (http://forum.xda-developers.com/showthread.php?t=1562890) thread before you start in on any thing. There was an issue with old recoveries and not being able to write over them.
Once you have your new recovery, there is a completely stock rom available (from AT&T), or you could use my stockish rom (link in my sig) based on the AT&T rom with all the bloat taken out, all the features left in, and with a few mods like the option to use the Holics or Faux kernels, and the advance power menu. It's very stable as I absolutely did not include any libs or junk ported from other phones.
Personally, if I were to stay on ICS, I would stay with Holics 1.3, with the kernel from 1.2. That was the most stable my phone has ever been (besides while running my rom of course, but I only used it for a few weeks as I have been able to use JB as my daily driver for a few months now )
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
Hi I've had my HTC one since june/july and decided I get on the rooting bang wagon.
Managed to unlock bootloader and everything looked fine, tried to install kitkat rom and well it went down hill from there as it wouldn't install and after that wouldn't do anything other than reload into cwn recovery. I'd not done a back up like a clown or took note of any of my firmware, kernel versions. managed to learn how to push rom via adb and fastboot. thing is I panicked as I did'nt want a bricked fone and stuck on stock odex rom.
its runs fine but would really like to have uk unbranded rom and firmware back on or atleast know where to find it before I attempt to stick either google edition software or kitkat again but hopefully a little more succesful. I've also now managed to s-off
wolverineuk said:
Hi I've had my HTC one since june/july and decided I get on the rooting bang wagon.
Managed to unlock bootloader and everything looked fine, tried to install kitkat rom and well it went down hill from there as it wouldn't install and after that wouldn't do anything other than reload into cwn recovery. I'd not done a back up like a clown or took note of any of my firmware, kernel versions. managed to learn how to push rom via adb and fastboot. thing is I panicked as I did'nt want a bricked fone and stuck on stock odex rom.
its runs fine but would really like to have uk unbranded rom and firmware back on or atleast know where to find it before I attempt to stick either google edition software or kitkat again but hopefully a little more succesful. I've also now managed to s-off
Click to expand...
Click to collapse
As you managed to s-off, there are 2 ways. The first being to run the 1.28.401.7 RUU (http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/), to downgrade and then update to the latest.
Or easier way would be to flash the latest 3.62.401.1 GURU RESET ROM here: http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/ That includes the options to go to complete stock.
More info, can be found in the original thread found here: http://forum.xda-developers.com/showthread.php?t=2428276
Hi,
I got this phone today, and unlocked the bootloader using the htcdev website. I then flashed a rom, and wiped, and then flashed the boot.img using fastboot. It worked fine, but the cyanogenmod nightly wasn't very stable. I decided to flash a different rom, but I couldn't get anything else to work. The roms, now including the previous rom, don't boot past their boot animations and shut down and boot again. Any help would be much appreciated!
Also, when I power down from the bootloader it tries to start up again. I have to pull the battery.
Also, it's an AT&T version. ROM recommendations are needed, because I can't get anything to work. :'( Preferably de-sensitized. I've check the dev thread with all the ROMS and links.
Make sure you are doing full wipes for each rom and also flashing the boot image.
Sent from my HTC One
I do that
WildfireDEV said:
Make sure you are doing full wipes for each rom and also flashing the boot image.
Click to expand...
Click to collapse
Yeah, I do that, using the factory reset in twrp and then install the rom, and then I flash the boot image using
fastboot flash boot boot.img
which flashes it no problem. I did actually get the cyanogenmod to work, which is interesting.
Update
I've gotten a ROM to work. It's http://forum.xda-developers.com/showthread.php?t=1428726 A sensed ROM. Hmm...
Geckodudes said:
I've gotten a ROM to work. It's http://forum.xda-developers.com/showthread.php?t=1428726 A sensed ROM. Hmm...
Click to expand...
Click to collapse
You need to update to ICS first, otherwise it won't boot any JB or KitKat ROM.
Then S-off your device, it's really easy
Viajanteluz said:
You need to update to ICS first, otherwise it won't boot any JB or KitKat ROM.
Then S-off your device, it's really easy
Click to expand...
Click to collapse
Thanks! I'm running the "leaked" RUU which is supposed to update the firmware to ICS, right? Can you provide a link to S-off? I can't find anything. Well actually I can, but I can't understand it. :/
There you go: http://forum.xda-developers.com/showthread.php?t=2521157
I've changed CiD? because of Vodafone not updating to ICS.
Then upgraded with an AT&T ICS RUU - http://forum.xda-developers.com/showthread.php?t=2013122
Solved.
Viajanteluz said:
There you go: http://forum.xda-developers.com/showthread.php?t=2521157
I've changed CiD? because of Vodafone not updating to ICS.
Then upgraded with an AT&T ICS RUU - http://forum.xda-developers.com/showthread.php?t=2013122
Click to expand...
Click to collapse
Thanks. I updated to ICS and all the roms I've tried work great. Thanks a lot!
Geckodudes said:
Thanks. I updated to ICS and all the roms I've tried work great. Thanks a lot!
Click to expand...
Click to collapse
You're Welcome! :good: