Related
Hi,
I have been trying out a couple of custom roms and want to revert back to my backed up 3 rom. Problem is it wont boot after restoring, I'm assuming this is because I overwrote the boot.img to use the custom roms, is there anywhere I can get the stock boot.img for 3 branded phone please?
You can get it from the RUU
Anyone know where I can download a 3 ruu?
daz1uk said:
Anyone know where I can download a 3 ruu?
Click to expand...
Click to collapse
i reverted back to my backup 3 rom that came with the phone. but the problem was i needed the right boot.img. since i was on 1.26 firmware i flashed the 1.26 boot.img which i got from here
so what i did i flashed the boot.img then restored my backup and it worked. or you can restore then if it gives you bootloops then just go back into bootloader, fastboot and then just flash the boot.img from that thread and that is it.
worked for me so try it out..make sure you are on fully charged though
Can any of you please upload a full backup so I can restore to stock??
Can I still do this even if I have the latest hboot after a 1.28 OTA?
You need the 1.28 RUU (which doesn't exist) or a nandroid backup from someone on 1.28 (which isn't advisable)
You may have to stick with custom for now
EddyOS said:
You need the 1.28 RUU (which doesn't exist) or a nandroid backup from someone on 1.28 (which isn't advisable)
You may have to stick with custom for now
Click to expand...
Click to collapse
What could be the issues if I got a nandroid backup from someone on 1.28?
I'm assuming it could brick my device?
bleary said:
What could be the issues if I got a nandroid backup from someone on 1.28?
I'm assuming it could brick my device?
Click to expand...
Click to collapse
the best thing you could of done is make a backup of your own stock rom that came with the phone. that is what i did. i got my stock rom back up which is 3 branded and all i did was restored back and flashed the OTA update. when i restored it did not reboot. all it needed was the stock boot.img and stock recovery. and that was it it worked perfectly. so do not know what the RUU business and what it does but if you have a backup and flash the correct stock recovery and boot.img depending on what firmware your backup was you would be fine
NoobTerminator said:
the best thing you could of done is make a backup of your own stock rom that came with the phone. that is what i did. i got my stock rom back up which is 3 branded and all i did was restored back and flashed the OTA update. when i restored it did not reboot. all it needed was the stock boot.img and stock recovery. and that was it it worked perfectly. so do not know what the RUU business and what it does but if you have a backup and flash the correct stock recovery and boot.img depending on what firmware your backup was you would be fine
Click to expand...
Click to collapse
I kicked myself when I done it as I jumped straight in completely forgot to backup my device first, which I always have in the past...frustrating!
Just want to get back to Three UK stock now, as sick of flashing every custom rom that is released lol
So as I have no backup and HTC/Three seem uninterested...I am screwed.
bleary said:
I kicked myself when I done it as I jumped straight in completely forgot to backup my device first, which I always have in the past...frustrating!
Just want to get back to Three UK stock now, as sick of flashing every custom rom that is released lol
So as I have no backup and HTC/Three seem uninterested...I am screwed.
Click to expand...
Click to collapse
you are not screwed mate..just do as Eddy said..apologies i do not know the procedure regarding how to flash RUU but i am sure there are guides in the development section for that
NoobTerminator said:
you are not screwed mate..just do as Eddy said..apologies i do not know the procedure regarding how to flash RUU but i am sure there are guides in the development section for that
Click to expand...
Click to collapse
Three/HTC have not released the 1.28 RUU mate, so if I try and use all there is (1.26 RUU) it fails as my hboot is now a newer version after the 1.28 OTA from three.
And I have no nandroid backup.
Oops.
bleary said:
Three/HTC have not released the 1.28 RUU mate, so if I try and use all there is (1.26 RUU) it fails as my hboot is now a newer version after the 1.28 OTA from three.
And I have no nandroid backup.
Oops.
Click to expand...
Click to collapse
ahh then i do not know then buddy sorry
You need to wait for the 1.28 RUU mate.
Don't use a nandroid backup from someone else as all info from that nandroid backup will be for the owners device and not yours. So if you send it to HTC they'll see the serial numbers don't match up. Plus the nandroid will have personal data from the owner on most of the time.
ahmadcentral said:
You need to wait for the 1.28 RUU mate.
Don't use a nandroid backup from someone else as all info from that nandroid backup will be for the owners device and not yours. So if you send it to HTC they'll see the serial numbers don't match up. Plus the nandroid will have personal data from the owner on most of the time.
Click to expand...
Click to collapse
Ah so it has as much detailed info as that, not just purely software. Thanks for the head sup mate. I will wait for the 1.28 RUU.
Do you know who is responsible for releasing them btw...network or HTC?
bleary said:
Ah so it has as much detailed info as that, not just purely software. Thanks for the head sup mate. I will wait for the 1.28 RUU.
Do you know who is responsible for releasing them btw...network or HTC?
Click to expand...
Click to collapse
HTC releases them and it is up to the network to decide really when to release it due to the software i would presume that goes onto the branded handsets. which sucks really. just like say ICS when it came out. really it should of been a global release like ios for apple but due to OEM's like Samsung and htc we have to wait till they decide when to release it due to the customization they do to the updates..similar to the updates we should be getting but we have to wait for 3 to get their asses in check
NoobTerminator said:
HTC releases them and it is up to the network to decide really when to release it due to the software i would presume that goes onto the branded handsets. which sucks really. just like say ICS when it came out. really it should of been a global release like ios for apple but due to OEM's like Samsung and htc we have to wait till they decide when to release it due to the customization they do to the updates..similar to the updates we should be getting but we have to wait for 3 to get their asses in check
Click to expand...
Click to collapse
It really does suck being at the mercy of networks for these updates.
As you say with iOS for example, there is one version from Apple - keeps it simple!
Hey guys, please help me out. I tried reverting back to stock AT&T HTC One M8 but I seem to have managed to remove the entire OS. I was following a guide on here on how to revert back but whatever I did in RUU, it completely ruined the phone so far. I can't load past the HTC logo. I'm able to install a custom recovery program but I don't know how to get back to anything at this point. I'm going to try to flash a custom ROM and see if that works but ultimately I'd like to go back to completely stock ROM. Thank you for the responses in advance.
First, flash a ROM in recovery to get it working again. Secondly, read the guides on going back to stock more thoroughly and make sure you understand what you're actually doing before trying to go back to stock again (the same is true before you even think about unlocking the phone - why do something when you have no idea what to do if something goes wrong?!?!).
I know my response may sound harsh but if you'd read up on everything first before doing anything then this question wouldn't have to be asked over and over again by multiple people every day...
EddyOS said:
First, flash a ROM in recovery to get it working again. Secondly, read the guides on going back to stock more thoroughly and make sure you understand what you're actually doing before trying to go back to stock again (the same is true before you even think about unlocking the phone - why do something when you have no idea what to do if something goes wrong?!?!).
I know my response may sound harsh but if you'd read up on everything first before doing anything then this question wouldn't have to be asked over and over again by multiple people every day...
Click to expand...
Click to collapse
Thank you for the response, appreciate it! I do read almost everything before flashing my devices, I like to see what problems people encounter before I attempt to mess with my phone. But I just found my mistake I ran into. The guide I was reading was about going from GPE to Sense Stock (I had maybe 4hrs of sleep in my defense on being brain dead). I did flash back to a custom ROM for now, I'll just do some more further research on going back to stock sense. Is it just as simple as getting the ROM and flashing like the custom ROMs?
Jayanyway said:
Thank you for the response, appreciate it! I do read almost everything before flashing my devices, I like to see what problems people encounter before I attempt to mess with my phone. But I just found my mistake I ran into. The guide I was reading was about going from GPE to Sense Stock (I had maybe 4hrs of sleep in my defense on being brain dead). I did flash back to a custom ROM for now, I'll just do some more further research on going back to stock sense. Is it just as simple as getting the ROM and flashing like the custom ROMs?
Click to expand...
Click to collapse
So, were you running a GPe ROM or a Sense ROM? If you were running a Sense ROM you just need to restore a backup to get it back to stock. What software build was the phone on when you bought it new?
EddyOS said:
So, were you running a GPe ROM or a Sense ROM? If you were running a Sense ROM you just need to restore a backup to get it back to stock. What software build was the phone on when you bought it new?
Click to expand...
Click to collapse
I was on a Sense ROM. Android Revolution to be exact. And if you're talking about this number: 1.54.401.5 then I was that?
So just find a backup and restore to it? And that'll allow me to grab OTA updates too?
Jayanyway said:
I was on a Sense ROM. Android Revolution to be exact. And if you're talking about this number: 1.54.401.5 then I was that?
So just find a backup and restore to it? And that'll allow me to grab OTA updates too?
Click to expand...
Click to collapse
If your phone was on 1.54.401.5 when you first got it (or before you flashed a custom ROM), and if you're S-OFF, you can follow the guide in my signature to go back to 100% stock
EddyOS said:
If your phone was on 1.54.401.5 when you first got it (or before you flashed a custom ROM), and if you're S-OFF, you can follow the guide in my signature to go back to 100% stock
Click to expand...
Click to collapse
Now what if I'm not 100% sure what build number I was before messing with my phone? Good chance of bricking? And one last question I promise, If I do go back to stock Sense ROM, can I still be rooted. S-Off, bootloader unlocked and still receive OTA updates? Or would I have to lock down again? I did read your guide, I was just wondering if I would still receive em before I decide to do all this work again lol
I really appreciate the quick responses. You're awesome.
Jayanyway said:
Now what if I'm not 100% sure what build number I was before messing with my phone? Good chance of bricking? And one last question I promise, If I do go back to stock Sense ROM, can I still be rooted. S-Off, bootloader unlocked and still receive OTA updates? Or would I have to lock down again? I did read your guide, I was just wondering if I would still receive em before I decide to do all this work again lol
I really appreciate the quick responses. You're awesome.
Click to expand...
Click to collapse
If you're not sure on the original build then I wouldn't follow my guide. Do you know the CID of your phone? to check, run the following fastboot command:
fastboot getvar all
And post the results (blanking out the S/N and IMEI)
EddyOS said:
If you're not sure on the original build then I wouldn't follow my guide. Do you know the CID of your phone? to check, run the following fastboot command:
fastboot getvar all
And post the results (blanking out the S/N and IMEI)
Click to expand...
Click to collapse
Well I recently changed my CID to that 11111111 CID but here's what I got from that command:
Jayanyway said:
Well I recently changed my CID to that 11111111 CID but here's what I got from that command:
Click to expand...
Click to collapse
Looks like an AT&T model to me.
Something that is not clear to me: Did you convert your phone to GPE or not? The partiton sizes are different so, if you did a GPE conversion you would need to convert your firmware partitions back.
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
exad said:
Looks like an AT&T model to me.
Something that is not clear to me: Did you convert your phone to GPE or not? The partiton sizes are different so, if you did a GPE conversion you would need to convert your firmware partitions back.
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
Click to expand...
Click to collapse
Yes, I have an AT&T HTC One M8. As far as I know, I never converted to GPE. Here's a history of what I've done as far as flashing goes.
Unlocked bootload, rooted, went S-Off, flashed Android Revolution, flashed Viper ROM, went back to Android Revolution then tried to go back to stock and broke my phone. Now I'm back on Android Revolution. I did a whole bunch of factory resets/dalvik wipes and such so maybe that's why it looks confusing?
exad said:
If you didn't convert to GPE, you should just be able to restore a CWS__001 backup from the stock backups thread in the general section, flash stock recovery and download/install the OTA.
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Free mobile app
Same Problem?
Hey folks!
I have the same question I think and I don't want to open a new thread.
I flashed SinlessRom over ViperOne without converting to GPe and now I'm stuck in a bootloop...
Can I restore a CWS__001 backup from the stock backups thread, flash stock recovery and I'm good to go?
Edit: Ok, my m8 is working now after flashing ViperOne, because it fixed the partitions
Edit2: There is still no information about the os when I'm booting into the bootloader
Does nobody know, why there is no firmware version?
Missing OS in HBOOT resolution
Finally got the answer I was looking for!
Download the modified TWRP from here:
http://forum.xda-developers.com/showthread.php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
Lintux_ said:
Does nobody know, why there is no firmware version?
Click to expand...
Click to collapse
Deleted.
Sorry didn't see your post @RockStar2005
Disregard this message!!
HTCNerdYoda said:
Deleted.
Sorry didn't see your post @RockStar2005
Click to expand...
Click to collapse
Yoda,
Hey........ disregard my previous message. That version of TWRP DOES work (fixing "Blank OS" issue), HOWEVER........ I created a new backup using it and then tried to restore it over the weekend........... IT DIDN'T WORK! I think something is corrupted with it. So anyone who clicked on that link and got that version of twrp, delete it and ANY BACKUPS YOU CREATED WITH IT immediately. They are corrupted and useless.
Fortunately though, I was able to find a fully-operational version of TWRP over the weekend that has no issues and it too fixes the "Blank OS" problem too. Here you go:
http://themikmik.com/showthread.php?16278-SPRINT-RECOVERY-TWRP-Recovery-(UNOFFICIAL)-v2-7-0-4 (Control + F this: "Downloads TWRP Recovery 2.7.1.0 (DH) | Mirror (AFH) - build date: July 13, 2014". I downloaded from the Mirror link.)
Don't worry about it saying Sprint...... the dev CONFIRMED it works for all variants/carriers. So after creating a new backup using the standard twrp, I went back to stock recovery, re-flashed my most recent firmware (2.22.401.5), and then switched over to that new version of twrp........ created a new backup and then restored it using that new version. Worked like a charm!! And the "blank OS" issue........... gone! I highly recommend it!!
So please delete that old twrp and any backups you created using it, and you should be good to go!
P.S. My thanks to Midasgalp and also Captain Throwback!!
RockStar2005
Thanks.
Sent from my HTC One_M8 using XDA Free mobile app
Thanks.
Sent from my HTC One_M8 using XDA Free mobile app[/QUOTE]
Anytime buddy!
RockStar2005
Hey everyone,
So here's what I've done on my phone:
Unlocked Bootloader
Installed TWRP
Rooted
Flashed custom ROM with kernel (specifically SkyDragon with its kernel)
I am still S-ON
Now I want to go back to stock. I found this thread: http://forum.xda-developers.com/showthread.php?t=2696147
Can I just follow the steps (unzip the file, put it in the folder, and use restore in TWRP) and then go back to stock (with the root the OP said)?
Thanks
RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Grab your CID nandroid from link provided, unpack it into TWRP/Philz backup folder, restore. Flash back stock recovery if you prefer(a MUST if you want to do OTAs)
BerndM14 said:
RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Grab your CID nandroid from link provided, unpack it into TWRP/Philz backup folder, restore. Flash back stock recovery if you prefer(a MUST if you want to do OTAs)
Click to expand...
Click to collapse
Thanks for the response. So this will return me back to stock without having to do anything else? Sorry I've been panicking for the past couple hours since I'm new to the M8 (previously flashed Nexus 4 constantly but M8 seems a lot harder)
Big Boy Marky said:
Thanks for the response. Will this return me back to stock?
Click to expand...
Click to collapse
Yes.
BerndM14 said:
Yes.
Click to expand...
Click to collapse
Alright thank you very much I'll give it a shot and give an update on what happens
BerndM14 said:
Yes.
Click to expand...
Click to collapse
Just to make sure, my cidnum is CWS__001 so I just download the
1.58.502.1 - TWRP Thanks to MLIGN
and then restore from that?
Big Boy Marky said:
Just to make sure, my cidnum is CWS__001 so I just download the
1.58.502.1 - TWRP Thanks to MLIGN
and then restore from that?
Click to expand...
Click to collapse
Yes.
What version did you have before putting custom ROM on? Was it 1.58 or 2.x?
If it was 1.58.502.1 you can also run the RUU for AT&T
But even if it's 2.x you can still restore the 1.58 and restore it, put on a stock recovery and let the OTA's roll :good:
BerndM14 said:
Yes.
What version did you have before putting custom ROM on? Was it 1.58 or 2.x?
If it was 1.58.502.1 you can also run the RUU for AT&T
But even if it's 2.x you can still restore the 1.58 and restore it, put on a stock recovery and let the OTA's roll :good:
Click to expand...
Click to collapse
Not really sure.... Right now I'm figuring out how to get the folder onto my internal sd card.. only problem is I can't even boot into the phone. I can sideload it but it'll be a zip and I can't seem to figure out how to unzip in TWRP....
BerndM14 said:
Yes.
What version did you have before putting custom ROM on? Was it 1.58 or 2.x?
If it was 1.58.502.1 you can also run the RUU for AT&T
But even if it's 2.x you can still restore the 1.58 and restore it, put on a stock recovery and let the OTA's roll :good:
Click to expand...
Click to collapse
Depending on why you are wanting to return to stock, you might consider that the Developer Edition phone is the same model as the AT&T phone - only the CID are different (MID is the same). I'm an AT&T customer and I've been running the Developer Edition software since about day 3 (I waited to make sure the phone was okay) and I have had zero problems with it. The only thing I sorta miss is Visual Voicemail, but otherwise I've been happier than a clam.
You do have to S-off to switch the CID if you want OTA updates, but a nandroid backup would probably work fine as well.
Big Boy Marky said:
Not really sure.... Right now I'm figuring out how to get the folder onto my internal sd card.. only problem is I can't even boot into the phone. I can sideload it but it'll be a zip and I can't seem to figure out how to unzip in TWRP....
Click to expand...
Click to collapse
You can mount the partitions in recovery though, so you should still be able to see it when connected to PC then you can just copy it over that way.
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
jshamlet said:
Depending on why you are wanting to return to stock, you might consider that the Developer Edition phone is the same model as the AT&T phone - only the CID are different (MID is the same). I'm an AT&T customer and I've been running the Developer Edition software since about day 3 (I waited to make sure the phone was okay) and I have had zero problems with it. The only thing I sorta miss is Visual Voicemail, but otherwise I've been happier than a clam.
You do have to S-off to switch the CID if you want OTA updates, but a nandroid backup would probably work fine as well.
Click to expand...
Click to collapse
Yeah, I would have suggested that as well but he's S-ON so...
It'll be much better to go Developer Edition, like you said model is the same, shouldn't have problems with radio etc and you'll definitely get updates at a much faster rate than sticking with AT&T. Seems they still use the Telegram to push OTA's which is why 4.4.4 is months behind.
BerndM14 said:
You can mount the partitions in recovery though, so you should still be able to see it when connected to PC then you can just copy it over that way.
Click to expand...
Click to collapse
Which partition would I mount? It only lets me mount Data, System, and one other thing but none of those make it discoverable in my computer. I just reflashed the ROM and am hoping it doesn't crash before I finish copying the file *fingers crossed*
I would have liked to S-OFF if possible but not sure anymore about that seeing how the only way is through sunshine :c
Back to stock thanks so much !
BerndM14 said:
Seems they still use the Telegram to push OTA's which is why 4.4.4 is months behind.
Click to expand...
Click to collapse
Telegram? Are you kidding? Somewhere out there is a pony with a thumbdrive on his back racing towards Taiwan.
Can't get back to stock.
BerndM14 said:
RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Grab your CID nandroid from link provided, unpack it into TWRP/Philz backup folder, restore. Flash back stock recovery if you prefer(a MUST if you want to do OTAs)
Click to expand...
Click to collapse
Big Boy Marky,
I have a similar problem. I had Insert Coin ROM installed. My Microphone is not working, so I want to send it back because the M8 is still under warranty. I flashed with the stock RUU, but the bootloader had re-locked. I unlocked bootloader again to root the phone in order to get the bootloader back to "Locked State." While rooting I crashed into a wall while installing superuser and I can't get binaries installed in order to be rooted. I have a HTC one M8 At&T Harmon Kardon Edition. Anything I can do to get it back to factory stock?
Thanks,
Teknokill
Hey guys,
I'm currently running a HTC One M8 with Skydragon GPE rom w Kitkat.
I was just wondering if I need to flash a Sense ROM first before proceeding to converting my phone back to full stock?
I'm also S-on.
Thanks for your help!
viscuosity said:
Hey guys,
I'm currently running a HTC One M8 with Skydragon GPE rom w Kitkat.
I was just wondering if I need to flash a Sense ROM first before proceeding to converting my phone back to full stock?
I'm also S-on.
Thanks for your help!
Click to expand...
Click to collapse
Run the splash they provide to return to Sense, then run the appropriate RUU for your MID to make sure you are re-partitioned correctly.
xunholyx said:
Run the splash they provide to return to Sense, then run the appropriate RUU for your MID to make sure you are re-partitioned correctly.
Click to expand...
Click to collapse
Hey, I appreciate the reply. But I read somewhere that this is only applicable if I converted my device to GPE. Im only running a GPE ROM.
My device was originally running Sense 6.
Hello currently I am using a T-Mobile m9 with a custom Rom. I used to own an m7 before I ditched it for my nexus 5. Today I noticed a security patches released and realized I can't remember how to update when not stock. I was wondering does flashing new firmware still work the same as it did on the m7?
As far as I know, there are RUU files in 2 different formats: exe file which runs form your computer, or .zip files, which are saved on the SD card and then once you boot in download mode it will automatically ask if you want to apply the RUU file; I think you need to be S-OFF for this method though (as soon as I got back to S-ON, flashing the RUU zip outputs an error)
MrGriffdude said:
Hello currently I am using a T-Mobile m9 with a custom Rom. I used to own an m7 before I ditched it for my nexus 5. Today I noticed a security patches released and realized I can't remember how to update when not stock. I was wondering does flashing new firmware still work the same as it did on the m7?
Click to expand...
Click to collapse
I would look to the thread for the rom you are using, there will be the rom updates and info that will point you in the correct direction.
You need to be aware of the phone status (cid/locked/unlocked/S status) but the thread is the correct place to get all the info
Since you are using a custom Tom I'm assuming you've installed twrp and rooted?
If so, and you didn't follow the procedure to properly backup your system for OTAs then RUU is your way to go (assuming you're not soft).
Anyway head to twrp thread in original m9 development forum and see what are your options.
Sent from my HTC One M9 using Tapatalk
Jhonys said:
Since you are using a custom Tom I'm assuming you've installed twrp and rooted?
If so, and you didn't follow the procedure to properly backup your system for OTAs then RUU is your way to go (assuming you're not soft).
Anyway head to twrp thread in original m9 development forum and see what are your options.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
i am s-off but i do not have a stock back up
MrGriffdude said:
i am s-off but i do not have a stock back up
Click to expand...
Click to collapse
In that case just follow this thread