Develop Bugs

[Q] URGENT!!! Reverting back to 3UK Rom

I'm very sorry this is such a noobish question but i was wondering if i could get some help by the people who know what they're doing.
So far what i've done is the following
1- Unlock the bootloader
2- Install Clockwork mod recovery
3- Flash 1.28 firmware
4- Install custom rom (leedroid) + flash boot.img
5- Root phone
Now i've descovered my phone has a few issues and i am entitled to send it back for a replacement.
Could someone tell me the order of how i can undo all the above. I have a nandroid of the original rom. Do i flash that first and then go from there? I need it to be exactly the same as when i first bought it.
Links to guides would be great. Thank you for your help

ahmadcentral said:
I'm very sorry this is such a noobish question but i was wondering if i could get some help by the people who know what they're doing.
So far what i've done is the following
1- Unlock the bootloader
2- Install Clockwork mod recovery
3- Flash 1.28 firmware
4- Install custom rom (leedroid) + flash boot.img
5- Root phone
Now i've descovered my phone has a few issues and i am entitled to send it back for a replacement.
Could someone tell me the order of how i can undo all the above. I have a nandroid of the original rom. Do i flash that first and then go from there? I need it to be exactly the same as when i first bought it.
Links to guides would be great. Thank you for your help
Click to expand...
Click to collapse
If you have a nandroid backup when you flashed custom recovery then restore the backup and relock the bootloader.

shadowboy23 said:
If you have a nandroid backup when you flashed custom recovery then restore the backup and relock the bootloader.
Click to expand...
Click to collapse
Thanks,
Once i've got the nandroid backup done do i flash the stock recovery, then relock the bootloader?
So once thats done no one will be able to know anything has been done to it, correct?

ahmadcentral said:
Thanks,
Once i've got the nandroid backup done do i flash the stock recovery, then relock the bootloader?
So once thats done no one will be able to know anything has been done to it, correct?
Click to expand...
Click to collapse
They can still tell that you have unlocked the bootloader because it will say "RELOCKED" and not even flashing the RUU for the carrier of your phone will do anything because it will still say "RELOCKED"

Would that stop a UK company from exchanging my phone for hardware defects?

ahmadcentral said:
Would that stop a UK company from exchanging my phone for hardware defects?
Click to expand...
Click to collapse
I am not sure. HTC reckons we void the warranty by unlocking the bootloader. But if you have bought it from a shop they tend to just turn the phone ON and look at the problem and they should swap it for another handset or give you a refund. Sales person normally don't get into the bootloader to check out anything. They more than likely have a look at the problem with the software or hardware defects. But if they decide to send it back to HTC then you might not get it replaced.

Ok,
Thanks for your help mate
Hope it gets replaced with one with no issues!

Also forgot to mention once you have restored your nandroid backup, flash the stock recovery and then relock the bootloader.

If you have a nandroid backup when you flashed custom recovery then restore the backup and relock the bootloader.
And if one happens to be the sort of complete fool that forgets the nandroid backup because they were too interested/ wrapped up in all the adb stuff to have remembered this what does one do with a 3 phone? Are there no 3 ruus in the wild at all? None listed on the file forum place.

oisindubh said:
If you have a nandroid backup when you flashed custom recovery then restore the backup and relock the bootloader.
And if one happens to be the sort of complete fool that forgets the nandroid backup because they were too interested/ wrapped up in all the adb stuff to have remembered this what does one do with a 3 phone? Are there no 3 ruus in the wild at all? None listed on the file forum place.
Click to expand...
Click to collapse
I have to admit I am such a fool. But lucky for me my phone is unbranded and has the HK 1.26.708.2 ROM which is in the list so that saved my ass. But for 3UK you might have to wait a bit until someone uploads it. I'm pretty sure it will appear sometime just don't know when.

im in a similar situation apart from i installed ARHD rom and i do have a backup of stock rom from when i installed cwm but my problem is, i flash backup and then flashed stock recovery but when i lock the bootloader and reboot i get greeted by the 1st htc logo then the screen flashes and the same logo appears but under it is some red writing that says something about being a development build and then it boots its self into fastboot but then if i unlock bootloader again the phone boots backed up stock rom fine!?
mines getting picked up on tuesday but i suppose on a plus side a courier is dropping me a replacement and taking my old one away at the same time, so unless the courier starts booting into hboot i should be ok lol

Give me half an hour and I can upload it for you.
Sent from my HTC One X using Tapatalk 2

http://db.tt/gWPc1RMq
It's still uploading at the moment but shouldn't take long.
Sent from my HTC One X using Tapatalk 2

daz1uk said:
http://db.tt/gWPc1RMq
It's still uploading at the moment but shouldn't take long.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Link doesn't work mate?
What's it supposed to be?

Ok guys, so today i flashed the nandroid backup but now i'm just stuck at the white HTC boot screen.
No idea what to do next?
Is it because i was on 1.28 firmware and restored down to a nandroid with 1.26? Is it because i haven't flashed stock recovery yet?
Really need help as i need this done before tomorrow UK time.
Thank You

bump.
I really need help now.
I have nothing on the root of SD card so i can't even flash a custom rom. What do i need to do to get my phone working?

[Q] Backup before Rooting

Hi
I have an unbranded (unlocked) HTC One X (Bought in UK). I recently received 4.1.1 update but I have decided that I want to root my phone. I have never rooted any phone before so I am pretty much new to the whole process.
I would really like to back up my phone as it is. I am not sure if it is possible to create a ROM of the current state of the phone and restore it if I want to. This is because my phone is still under warranty and if it goes faulty I would like to send it back to HTC in its original state.
I can backup my contacts, messages, apps etc. separately. It is the actual original HTC software I am more worried about.
Any help would be appreciated.
Thank you

Anyone please?
I have been browsing through the forum and I have seen few people ask very similar questions but no one seem to have figured it out yet. I have also seen many topics where people are struggling to recover back to stock ROM because they did not make any proper backups.
Any help will be appreciated.
Thanks

So you need 3.14.401.27 RUU. You are on 2.17.401.x now?
Check htcruu.com, the UK ROM is widely available.

BenPope said:
So you need 3.14.401.27 RUU. You are on 2.17.401.x now?
Check htcruu.com, the UK ROM is widely available.
Click to expand...
Click to collapse
Thanks for the reply.
I have official HTC 3.14.401.27 installed on my phone right now. I have never rooted it or anything. That is why I am asking if there is a way for me to save that as a ROM or save that ruu before I root my phone.

Make sure you make a nandroid backup of your stock rom after unlocking bootloader and installing clockworkmod recovery, and keep that backup in a safe place.

Cocktopus said:
Make sure you make a nandroid backup of your stock rom after unlocking bootloader and installing clockworkmod recovery, and keep that backup in a safe place.
Click to expand...
Click to collapse
Okay thanks. Any other way to make a copy of stock kernel and recovery too?

i believe there are links to stock kernels and stock recoveries. there's also a thread to go back from custom rom to stock rom if ever you change your mind

jinogungon said:
i believe there are links to stock kernels and stock recoveries. there's also a thread to go back from custom rom to stock rom if ever you change your mind
Click to expand...
Click to collapse
Yup I have been reading that.
But it says that:
These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
After checking my phone, it seems like I have 1.33. It seems like there is no way for my phone to get back to stock at the minute. That is why I was asking if there is anything else I can do to make it possible before I actually root my phone.

HTC One X VODAP102 RUU

I'd like to unroot my phone and go back to stock, coming from AOSP 4.2.2. My CID is VODAP102, is the anyone who happens to have a link to the RUU file of it?
since www.htcruu.com is down...

Solarr said:
I'd like to unroot my phone and go back to stock, coming from AOSP 4.2.2. My CID is VODAP102, is the anyone who happens to have a link to the RUU file of it?
since www.htcruu.com is down...
Click to expand...
Click to collapse
As far as I know, there is no RUU for this CID, but you could use nandroid instead. Try HERE, you will find what you need.
Also, check you main version, this is also important when choosing correct nandroid (and RUU, also).

[email protected]|-|oR said:
As far as I know, there is no RUU for this CID, but you could use nandroid instead. Try HERE, you will find what you need.
Also, check you main version, this is also important when choosing correct nandroid (and RUU, also).
Click to expand...
Click to collapse
Thanks for your reply.
My main version is 2.17.161.4, which is not listed with VODAP102. Should I take an other one, like VODAP001/2.17.161.4 or isn't this possible?

Solarr said:
Thanks for your reply.
My main version is 2.17.161.4, which is not listed with VODAP102. Should I take an other one, like VODAP001/2.17.161.4 or isn't this possible?
Click to expand...
Click to collapse
Actually, main version is more important for nandroid
I thought you were on JB already, sorry.
If you want to upgrade, use 2.17.161.4 nandroid, then flash OTA update, and then just choose custom ROM you want, or stay with crappy Voda stock :crying:
I went exactly the same way, and my One X is rocking Renovate Final 2 with xm #192. I love it!

[email protected]|-|oR said:
Actually, main version is more important for nandroid
I thought you were on JB already, sorry.
If you want to upgrade, use 2.17.161.4 nandroid, then flash OTA update, and then just choose custom ROM you want, or stay with crappy Voda stock :crying:
I went exactly the same way, and my One X is rocking Renovate Final 2 with xm #192. I love it!
Click to expand...
Click to collapse
I am on JB already (4.2.2). But I want to downgrade to my stock HTC (crappy Voda :crying rom.
So I shoud be just fine if I choose to nandrestore to 2.17.161.4 CID VODAP001, since the mainver is the same? Just for confirmation, I dont like to mess things up.
What happens to my CID after restore, since it is different? And my HBOOT?

Solarr said:
I am on JB already (4.2.2). But I want to downgrade to my stock HTC (crappy Voda :crying rom.
So I shoud be just fine if I choose to nandrestore to 2.17.161.4 CID VODAP001, since the mainver is the same? Just for confirmation, I dont like to mess things up.
What happens to my CID after restore, since it is different? And my HBOOT?
Click to expand...
Click to collapse
I am not really sure about downgrading. Try searching here, I remember there were some threads about it.
CID is hardcoded to your phone, so it cannot be changed unless S-OFF (which is not coming soon to One X). HBOOT also should remain the same.
But, why in the world you would go back? Why don't you flash some custom ROM instead and enjoy the life? I would strongly recommend you to try Renovate, and then decide. :good:

Yeah with that nandroid you can fool the bootloader, restore it and also flash back the stock 2.17 stock recovery. You should be able to update to JB stock with official ota.
Your cid will be listed as the same as the nandroid backup but will be corrected when you do the ota.

Solarr said:
I am on JB already (4.2.2). But I want to downgrade to my stock HTC (crappy Voda :crying rom.
So I shoud be just fine if I choose to nandrestore to 2.17.161.4 CID VODAP001, since the mainver is the same? Just for confirmation, I dont like to mess things up.
What happens to my CID after restore, since it is different? And my HBOOT?
Click to expand...
Click to collapse
Wait a bit, I read again your posting here.
If I'm not wrong, what you want is to unroot and revert to stock, right?
Solarr said:
I'd like to unroot my phone and go back to stock, coming from AOSP 4.2.2. My CID is VODAP102, is the anyone who happens to have a link to the RUU file of it?
since www.htcruu.com is down...
Click to expand...
Click to collapse
Okay, if so, why would you go back to ICS? I mean, nandroid mentioned in my post:
[email protected]|-|oR said:
As far as I know, there is no RUU for this CID, but you could use nandroid instead. Try HERE, you will find what you need.
Also, check you main version, this is also important when choosing correct nandroid (and RUU, also).
Click to expand...
Click to collapse
is also stock Voda, but JB.
If you want to sell it, it's just as good as ICS stock. If you want to service it, it's the same.
Nandroid that I posted is made from pure Voda JB stock, just after the OTA upgrade.

He can't run the JB version yet....when the main version is 2.17 ! He's on JB aosp....those roms also boots on the lower hboots. He should go back to stock and update .....

Mr Hofs said:
He can't run the JB version yet....when the main version is 2.17 ! He's on JB aosp....those roms also boots on the lower hboots. He should go back to stock and update .....
Click to expand...
Click to collapse
Alright, I see. Again, I was not reading carefully.
So, he could restore 2.17 stock nandroid, and JB will come OTA, so he will be good.

[email protected]|-|oR said:
Alright, I see. Again, I was not reading carefully.
So, he could restore 2.17 stock nandroid, and JB will come OTA, so he will be good.
Click to expand...
Click to collapse
Correct !
Use the voda001 2.17.....copy it to the correct folder on the sdcard. Flash the boot.img with fastboot commands, perform a full wipe in recovery and restore the nandroid. Flash the stock 2.17 recovery and check in the phone settings - about - software updates to apply the official ota

[email protected]|-|oR said:
I am not really sure about downgrading. Try searching here, I remember there were some threads about it.
CID is hardcoded to your phone, so it cannot be changed unless S-OFF (which is not coming soon to One X). HBOOT also should remain the same.
But, why in the world you would go back? Why don't you flash some custom ROM instead and enjoy the life? I would strongly recommend you to try Renovate, and then decide. :good:
Click to expand...
Click to collapse
Maybe I'll try Renovate Final 3 sometime, but first I want to revert it back to stock to return it to the store because of a hardware (camera) problem.
edit: Didn't see the second page. Thanks Mr Hofs! I'll try it out tomorrow!

Solarr said:
Maybe I'll try Renovate Final 3 sometime, but first I want to revert it back to stock to return it to the store because of a hardware (camera) problem.
edit: Didn't see the second page. Thanks Mr Hofs! I'll try it out tomorrow!
Click to expand...
Click to collapse
Mr Hofs said:
Correct !
Use the voda001 2.17.....copy it to the correct folder on the sdcard. Flash the boot.img with fastboot commands, perform a full wipe in recovery and restore the nandroid. Flash the stock 2.17 recovery and check in the phone settings - about - software updates to apply the official ota
Click to expand...
Click to collapse
Just a little warning to Solarr - because I've done it. You may need to follow this procedure:
What if i get MD5 Mismatch?
type in teminal:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/Name_of_the_nandbackup_folder
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
because the folder name may not be cwm compatible. Don't worry, if you get the mismatch message, just do the above, and you will be alright. :good:
At first boot, you will get one small OTA first, and then the big one with JB update.
Good luck!

[email protected]|-|oR said:
Just a little warning to Solarr - because I've done it. You may need to follow this procedure:
because the folder name may not be cwm compatible. Don't worry, if you get the mismatch message, just do the above, and you will be alright. :good:
At first boot, you will get one small OTA first, and then the big one with JB update.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I couldn't wait to try it out so I already flashed it just before you posted. I did get the mismatch, so I removed all spaces from the foldername which did exactly the same job. Thanks anyway!
It works, I'm going to try to do an OTA update right now.

Got it all stock and running, thank you very much!

No problem !
CASE CLOSED !

So I've managed to remove the whole OS...

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

[Q] On custom ROM but want to go back to stock?

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