Related
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
I'm sorry if somebody already posted that, i swear I had a look
I have a SIM unlocked AT&T MB860 Atrix with gingerblur 4.5, and I would like to try some real gingerbread goods, which means bootloader unlock and 2.3.4 HKTW.
Do I have to flash back to 1.8.3 stock sbf before actually unlocking and installing gingerbread? I heard people saying is not safe to flash sbf for SIM-Unlocked Atrix because it can cause Wi-Fi problems, is it still the case?
Second problem: I had my phone rooted, but now I don't have an external micro SD card, so I wouldn't be able to root with gingerbreak-similar methods, is this a deal breaker or there is another way to complete the process all the way through?
Thanks a lot
As a general rule, it's best to flash back to stock before flashing anything else. Because Gingerblur requires Tenfar's recovery to run, I believe this will be the best way to do this. If someone else could chime in about the SIM-unlock/wifi issue, that would be great.
As for the rooting method on 2.3.4 HKTW, it works by installing a ZIP through recovery. In my own experience, it only seems to read external SD cards. If you can make it read the internal somehow, then you should be able to root.
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
dLo GSR said:
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
Click to expand...
Click to collapse
Good to know, thanks!
Did you clear data or anything like that after flashing?
jwhited said:
Good to know, thanks!
Did you clear data or anything like that after flashing?
Click to expand...
Click to collapse
oh, right, forgot. i did do the fastboot -w beforehand.
i have simunlocked atrix as well, it makes no difference.
I went from Greyblur straight to GB with no issues.
Thanks guys
This is worth a try
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
kshiuan said:
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
Click to expand...
Click to collapse
I just did this tonight, and for some reason, I had some problems flashing the 1.8.3 SBF directly. So I downloaded the 1.2.6 (shipping) firmware and just did the updates.
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
its been said before that once you're unlocked, you're always unlocked. Flash a fruitcake for a stock setting.
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
xploited said:
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
Click to expand...
Click to collapse
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Pizzaapu said:
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Click to expand...
Click to collapse
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
Lol hes returning back to Moto anyways ha ha! I'll try it out, I fastbooted to Gingerbread (via Kenn) So I never did the OTA.... so I guess I am safe.
Per this post, you can tell if you've flashed OTA 2.3.4. If it has been flashed already, then DO NOT downgrade to a official 2.2.2 build.
mysticdrew said:
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
Click to expand...
Click to collapse
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Sass86 said:
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Click to expand...
Click to collapse
Yeah but doesn't using the pudding 2.3.4 (4.5.91) still makes you have the "Unlocked" thing on the boot setting? which is what the OP wants to avoid so if he takes it to like AT&T if they see it and see Unlocked they will void the warranty, I am pretty sure the retail story wont extract his phone to see if the fuse it sparked and unlocked.
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
I am not sure about the sbf, but I can tell you for sure fruitcake will not get rid of the unlock logo, flashing a fruitcake is only a stock ROM.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
No. Only if you haven't upgraded via ota update. If you did, then there is no way of removing "unlocked" yet.
My overclocked alien atrix
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Just a thought... did you ever back up your PDS partition?
Touchscreen issues sometimes are due to pds issues. If you have made a backup, wouldn't be a bad idea to try restoring it to see if that fixes your issue.
If you didn't back it up, take a look at this thread with a pds file that helped others.
http://forum.xda-developers.com/showthread.php?t=1131649
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
Probably a long shot but, I used to have very similar issues with other phones in the past when I've had a screen protector on for awhile and it gets scratched up. Maybe try remove the screen protector if there is one and see what happens.
If it is going back for repair. why not intentionally hard brick it? The first thing they will do is the full blown factory flash, erasing all evidence.
If you do this, make certain you give them a story that somehow describes both the actual problem and the bricked condition (else they might think the un-bricking fixed it and not catch the other issue.
EDIT: Maybe not all evidence, the fuse that was blown when you unlocked a 2.3.4 might be a real hardware type fuse and never be cleared. Don't know.
My device is doing this exact same thing and I'm in the same position you are in. I never backed up the PDS partition, but a backup using the image in the linked thread did not solve the problem. Nor did flashing multiple new ROMs.
I'm not sure if this is a hardware or software problem. It problem seems to go away if you lock the screen a few times, but then later reapers.
Sorry to hijack this thread, but does anyone know if replacing the digitizer will fix this problem? Since I'm in New Zealand this would be an economic solution as shipping to and from the US is pricey.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Pizzaapu said:
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Click to expand...
Click to collapse
I just saw this. I ended up using the stock 2.3.4 sbf, and then doing a factory reset in the privacy menu. Now has all the stock info in the "about phone" section. I'll let you all know how it goes. Thanks for the suggestions.
Just got back from AT&T! they said it was a software issue! They gave me the warranty and gave me a refurbished Atrix with 1.8.3, stock froyo on it! I'll stay OTA until CM7 comes out of pre-beta then see how to root it after OTA : )
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
You should get it. But if any system files are changed by root, the OTA will not install. Otherwise, you should be good to go.
BTW, the Dev Edition 4.4.3 ROM is already posted in Development.
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
Make sure you restore all the bloatware as well or it won't update. I found this out with the last update. I would hold off on the update until you know it's safe to proceed without losing root unless you want to confirm it first for us. [emoji16]
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
volcalstone said:
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
Click to expand...
Click to collapse
redpoint73 said:
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
Click to expand...
Click to collapse
I got this nandroid (1.12.502.18 - TWRP 2.6.3.3 Thanks to Wonders_Never_Cease) from http://forum.xda-developers.com/showthread.php?t=2701376 and tried to restore, it ends abruptly leaving wifi and boot screen broken. Phone still boots in ARHD 10.1 but doesn' work perfectly. I put the folder from rar file under TWRP Backup folder and it picked up fine but won't restore. Maybe because I have TWRP 2.7.1.0?
I just picked up the phone and it is S-ON with bootloader unlocked/tempered. I'm trying to get back to stock till we have RUU to convert it to DE eventually like the M7.
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested. I also tried the HBOOT no PC required version of RUU but it would end abruptly at parsing. Maybe because I'm S-ON? I checked the MID and CID, they are both AT&T stock.
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
noobsquared said:
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested.
Click to expand...
Click to collapse
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
redpoint73 said:
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
Click to expand...
Click to collapse
Thanks for the links and everything man but the whole reason I'm trying to go back to completely stock is that I feel there is something wrong with my phone or maybe this is normal for M8. When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone. Tap on restart and it took a minute. First boot took well over 5 minutes. Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own. I may try the full AT&T 4.4.3 ROM since it's very close to stock. If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
noobsquared said:
When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone.
Click to expand...
Click to collapse
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
noobsquared said:
First boot took well over 5 minutes.
Click to expand...
Click to collapse
Totally normal on the first boot after any ROM flash.
noobsquared said:
Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own.
Click to expand...
Click to collapse
Ummm, not sure what is being said here "pimp on it's own". I'm guessing a typo or darned auto correct!
noobsquared said:
If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
Click to expand...
Click to collapse
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
redpoint73 said:
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
Click to expand...
Click to collapse
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on. I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
I will try to update the firmware and try to get on that AT&T Rom bandwagon to see how it goes. Thanks for all your help and input. I wish it wasn't so complicated with M8. M7 was so easy to mess with or maybe I got used to that lol
noobsquared said:
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
Click to expand...
Click to collapse
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
noobsquared said:
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on.
Click to expand...
Click to collapse
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
noobsquared said:
I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
Click to expand...
Click to collapse
FYI, as long as you are a current account holder, AT&T doesn't give a darn what you change in software, they will still honor the warranty if there is a hardware issue.
redpoint73 said:
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
Click to expand...
Click to collapse
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
Just an FYI- the black screen is a common problem with aroma installers and is well known.. All the other issues? I haven't a clue.
Hello!
I'm using 2.22 WWE version stock rom with 4.4.3, but I have long boots of device with old AT&T firmware.
Is there any way to update firmware?
I'm s-on, and firewater doesn't works.
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Thanks guys for all the help and support. I messed with the phone quite a bit and tried quite a few things and all the posts here help me learn a lot too. I was able to go all stock after s-off using that RUU method. I tried a couple other roms and finally back to dev edition stock for now. Was able to convert completely to stock with all the info and so far so good.
Once again, thanks a bunch everyone
Sent from my HTC One_M8 using XDA Free mobile app
iArtisan said:
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Click to expand...
Click to collapse
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
cachookaman said:
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I had to do the same thing but given that what a pain it is without s-off, I'm not complaining. $25 is a small fee to pay for the peace of mind that you ha e almost full control of the device now.
Sent from my HTC One_M8 using XDA Free mobile app