I am merely rooted, so no other mods. I did my over the air update to 4.5.141 last week and have had nothing but problems: spontaneous reboots, weird A2DP stuff (launching both music and beyond pod simultaneously and locking the phone!), poor battery life.
I want to go back to what was stable and worked, 2.3.4 (4.5.91) and am confused as to how to safely do this. From what I read, I cannot use the old SBF because it will brick the phone. I have not found the SPF for 2.3.4, anyway, so that is probably not important. I do not really want to use CWM and a new rom, I just want to use the phone. I root for WifiTether and Ti backup reasons only and do not need to do anything else. I can wait for Q4 for ICS, but not if it has all these problems over the next 10 months!
How can I go safely back to a stock 2.3.4?
Keithspg
The only thing I can think of is to unlock the bootloader (if possible) and flashing a fruitcake. I haven't read of anyone successfully unlocking the bootloader after the OTA AND having never unlocked it before but that doesn't mean it's not possible.
keithspg said:
I am merely rooted, so no other mods. I did my over the air update to 4.5.141 last week and have had nothing but problems: spontaneous reboots, weird A2DP stuff (launching both music and beyond pod simultaneously and locking the phone!), poor battery life.
I want to go back to what was stable and worked, 2.3.4 (4.5.91) and am confused as to how to safely do this. From what I read, I cannot use the old SBF because it will brick the phone. I have not found the SPF for 2.3.4, anyway, so that is probably not important. I do not really want to use CWM and a new rom, I just want to use the phone. I root for WifiTether and Ti backup reasons only and do not need to do anything else. I can wait for Q4 for ICS, but not if it has all these problems over the next 10 months!
How can I go safely back to a stock 2.3.4?
Keithspg
Click to expand...
Click to collapse
I'm with you Keith
I am also rooted for TI backup. Since the update WiFi has been randomly dropping. My ABC news app keeps losing connection when going to video section. While on Android IRC WiFi drops out and I have to reconnect. Before update WiFi remained connected for days.
I have way too much work into the phone to reformat to anything. I am hoping ICS upgrade will fix the problem but who knows what they will bring.
Since we are rooted there is no way Motorola will support us. We need a dev here to figure out what went wrong. (
Just backed up, wiped the phone (from fastboot menu), re-rooted, restored. Not an hour later, spontaneous power off while in my pocket. This really sucks. I can un-root, if that will fix it, but do not see how root can be causing the problem. Still have not unlocked the boot loader and would use that only as a last resort.
Regardless, it is not clear to me that the 3.2.4 unlock instructions will work with 3.2.6.
I do not know what a pudding or a fruitcake is, really. I have been reading about CM7 and it does not not appear as 'released' for Atrix. Also it looks like a hassle to add everything Google after you install it *and* the fingerprint sensor does not yet work with the alpha builds which do exist for Atrix.
not happy at all.
keithspg said:
Just backed up, wiped the phone (from fastboot menu), re-rooted, restored. Not an hour later, spontaneous power off while in my pocket. This really sucks. I can un-root, if that will fix it, but do not see how root can be causing the problem. Still have not unlocked the boot loader and would use that only as a last resort.
Regardless, it is not clear to me that the 3.2.4 unlock instructions will work with 3.2.6.
I do not know what a pudding or a fruitcake is, really. I have been reading about CM7 and it does not not appear as 'released' for Atrix. Also it looks like a hassle to add everything Google after you install it *and* the fingerprint sensor does not yet work with the alpha builds which do exist for Atrix.
not happy at all.
Click to expand...
Click to collapse
Adding the Google "everything" is actually very easy. Flash the gapps after the rom, then first time you go to market after signing in, it prompts you to install whatever google apps you want. As for the fingerprint, I'm on cm7 weekly build Feb 20 and I only use fingerprint to unlock. So it works. And its been very stable for me so far. Hth
Related
Ok, so first off, I was interested in the prospect of using the Droid3 camera because I heard it was better and supported high speed video recording (something that I really want on the Atrix) but I heard that you had to be Deodexed. Well, I knew that if I unlocked my bootloader and installed a custom ROM such as Alien or CherryPie, it would work, but I didn't want to unlock my bootloader. I was rooted though.
So then I decided to google how to manually deodex, and I came across the program xUltimate whatever, followed the directions (although it seemed to be intended for the Droid and not the Atrix, I don't think I should've done that) and part of the process through running xUltimate, I got a message saying that I was out of space on my Atrix relating to the process it was in the middle of doing, and was like, oh crap.
My phone didn't start, but I had made a recovery a couple of days earlier in Tenfar's CMW, so I went to restore that. Then when that was restoring, it froze on some process when it was restoring, and I let it try and try for hours, but to no avail, because it had been hours and it was still stuck on the same spot. So I restarted my phone.
Well, then upon my phone starting, everything was gone in terms of my apps, and the stock gingerbread background was there. I thought, well, maybe it's fine and I'll just restore my apps with TiBu, and everything will be fine. That wasn't the case at all because any app that I downloaded from the market with the exception of a few would automatically force close. So I couldn't get TiBu to work, or Superuser, or anything.
So at that point I knew that I had seriously messed up some files on my phone, and I decided I was gonna flash .sbf. So I got the stock 2.3.4 .sbf and flashed it with RSD Lite 5.3.1.
It flashed gingerbread, and when it rebooted, everything looked fine and dandy, but it was exactly the same problem, where apps would force close.
Then as a last hope of solving the problem I tried to use fastboot to recover my phone with the nandroid backup that I had made, but it said that the image file was too large. And that also probably has something to do with the fact that I can't actually use fastboot to do that unless I have an unlocked bootloader, right?
So my question is, how can I fix it? How can I start over fresh (since flashing .sbf didn't wipe everything) so that those system files that I messed with when I was running the deodexing utility are returned to their proper state?
I mean, at the moment, it works as a phone, it receives and makes calls, and I can send texts and take pictures, and use the stock browser, but no other app will open.
And secondly, has anyone gotten the 120fps video recording working with the d3 camera apk?
But of course, more importantly, how do I get out of this rut?
Thank you so much and I'm really sorry for writing so much, I just wanted to give you as much info as possible so that you could come up with the best answer. And I apologize for my stupidity,
Thanks again,
did you try a factory restore after the sbf flash? you have to do that to restore the phone to the orignal state. flashing the.sbf doesn't do it...
Sent from my MB860 using Tapatalk
thank you so much, after doing the factory reset, it works fine now. Now to go mess with it again hehehe.
Sent from my MB860 using XDA App
Glad your sorted as to your fastboot problem. Use moto fastboot as it splits large files for you.
Sent from my MB860 using XDA App
So, I thought I had fixed the problem, but after unlocking the bootloader, I installed Alien, and the radio is all wonky...I'm not getting service 99% of the time, and that's kinda really bad, and, yes I checked the APNs, and there were no problems there (at least I think, I restored default) and I even tried flashing a radio, which made no difference. And I know that flashing using RSD is bad but I didn't know better at the time so I reflashed stock Gingerbread 4.5.91, but the radio problem is still there.
And could someone tell me what I'm doing wrong because I've tried flashing two different roms (Alien and the Star Wars one) and it seems as if its not actually doing everything that it should, for example the star wars one, there is no camera app, or rather it force closes, and the bootanimation and boot image are stock at&t, and the lockscreen is default....and I even checked the build.prop which should have been modified for the d3 camera and it wasn't modified, which led me to think that anything that involved root access didn't work when flashing the rom. Further proof for that idea is that after I flashed either rom, I lost root access and had to re-root my phone.
This is really weird, and it's starting to bug me because now my phone can't even be used as a phone
Thank you for your help.
I'm finally getting around to updating my phone to 2.3.4 (bought a house over the summer and haven't had time to play with updates).
I currently have a rooted 2.2.2 Atrix with my apps/data backed up via Titanium Backup and saved off to my desktop for later restoration if needed. Except for Root and APN mod, the phone is otherwise stock.
I'm not necessarily interested in using a custom rom right now (though a wipe of data/apps may help clean things up), though I do need root, APN hack, and plan on installing the full-linux-webtop mod (if I can get my laptop dock to work reliably...). I assume things have evolved since the old posts I've come across about updating when it first came out.
What is the best method for updating to 2.3.4 at this stage?
thanks,
- David
In my opinion you should still unlock your phone even if you are staying with a stock rom. It is way easier to flash with CWM method, even if you are staying with a stock rom. Look at Fruitcake 2.3.4 and you can also flash a fruitcake 2.3.4 webtop. If you mess up your webtop hacking on it to get it just like you want it, your can reflash just the webtop.
Of course after you unlock your phone, you will probably get the itch to look at some of the custom roms that are out there. A lot of them are basically the stock rom with customizations built in.
I got my Atrix a few weeks ago (used, it was unlocked already), and have been having Sleep Of Death issues since day one. I finally got fed up, and flashed the full 4.5.141 sbf via RSDLite. The SODs dissapeared completely. I rooted, still no problems. Then I unlocked the BL and SODs returned. I tried with the Automatic Unlocker, and manually with the original pudding method. Same thing.
When I do the unlocks it says I'm already unlocked, the only thing that changes is the "Unlocked" text comes back on the boot screen. But if I don't flash the pudding I still cant use fastboot to flash recovery etc.
Does anybody have an idea on what could be the problem? Maybe it's because the pudding is for 4.5.91 BL?
Thank you
EDIT:
I flashed 4.5.91 stock (almost bricked my phone), and unlocked with pudding. Still had SODs, so it's not because of 4.5.141. Any help would be really appreciated.
I also sometimes get a red text saying: Unrecoverable bootloader error 0x00000004. And have to do a battery pull to restart the device.
eNorby said:
I got my Atrix a few weeks ago (used, it was unlocked already), and have been having Sleep Of Death issues since day one. I finally got fed up, and flashed the full 4.5.141 sbf via RSDLite. The SODs dissapeared completely. I rooted, still no problems. Then I unlocked the BL and SODs returned. I tried with the Automatic Unlocker, and manually with the original pudding method. Same thing.
When I do the unlocks it says I'm already unlocked, the only thing that changes is the "Unlocked" text comes back on the boot screen. But if I don't flash the pudding I still cant use fastboot to flash recovery etc.
Does anybody have an idea on what could be the problem? Maybe it's because the pudding is for 4.5.91 BL?
Thank you
Click to expand...
Click to collapse
Once the bootloader is unlocked you can't lock it back... its actually a fuse in hardware.
Sent from my MB860 running Jokersax's CM9
giqbal said:
Once the bootloader is unlocked you can't lock it back... its actually a fuse in hardware.
Sent from my MB860 running Jokersax's CM9
Click to expand...
Click to collapse
Yes, I get that. But when I flash the stock 4.5.141 sbf, the unlocked text dissapears. I understand that the BL is still technically unlocked, but for some reason I can't fastboot flash recovery, and similar stuff. Only after I flash pudding. But then I get SODs.
Stupid sod
eNorby said:
Yes, I get that. But when I flash the stock 4.5.141 sbf, the unlocked text dissapears. I understand that the BL is still technically unlocked, but for some reason I can't fastboot flash recovery, and similar stuff. Only after I flash pudding. But then I get SODs.
Click to expand...
Click to collapse
I installed advanced wifi lock from the market and that's helped with my SOD issues.
I used a wakelock app. but it drained my battery fast. I want a real solution. Now that I know what causes the SODs, I'm determined to fix them. I'm on stock for now with no SODs what so ever.
Sent from my MB860 using XDA
flashed 4.5.91 and unlocked. still got SOD...
bump.
Someone have any ideas?
bump
bump. please?
Its not the pudding thats causing it - Otherwise everyone here with an unlocked bootloader would be *****ing about it.... Its an app or something else you've installed that doesn't agree with something else. You'll have to spend the time tracking them down one by one. Its a PITA, but your only real option. Best bet - completely wipe everything after a full backup, and then start from scratch.
G-Man. said:
Its not the pudding thats causing it - Otherwise everyone here with an unlocked bootloader would be *****ing about it.... Its an app or something else you've installed that doesn't agree with something else. You'll have to spend the time tracking them down one by one. Its a PITA, but your only real option. Best bet - completely wipe everything after a full backup, and then start from scratch.
Click to expand...
Click to collapse
I already tried that. Wiped at least a dozen times, tried all the ROMs available, all the kernels, all the radios. It's the unlocked BL that is causing it. And I'm not the only one with this problem, I read about others in another thread. I don't know why only a few of us are getting this. But I'm 100% sure it's because of pudding. Because flashing back the stock BL (via rsd lite) fixes it.
Stock MotoBlur, with the locked bootloader works fine. As soon as I flash pudding (and that is the only thing I change) the reboots and SODs return.
There has to be an issue with your device then, otherwise every single person would have the same issue. Its not the pudding... If it was, EVERYONE would have this issue. Its your device, or something else on it.
G-Man. said:
There has to be an issue with your device then, otherwise every single person would have the same issue. Its not the pudding... If it was, EVERYONE would have this issue. Its your device, or something else on it.
Click to expand...
Click to collapse
Yes, I get that. But what I want to know is what? What is the unlocked bootloader doing, that the locked one isn't?
Its more than likely a hardware issue... This was the case back when I had my Samsung Captivate.... Some builds had no issues, and others (newer builds) were plagued with random garbage that couldn't be resolved no matter what people tried to do... I've had my Atrix 4G since pre-release day, Feb 22nd of last year. Haven't had a single issue. Others who got theirs months later, or just recently, have had some issues that I dont know why they are having (Rescue Sqad Staff on a forum dedicated to the Atrix 4G and Atrix 2) Sometimes the only way to fix certain things are to replace the device.
G-Man. said:
Its more than likely a hardware issue... This was the case back when I had my Samsung Captivate.... Some builds had no issues, and others (newer builds) were plagued with random garbage that couldn't be resolved no matter what people tried to do... I've had my Atrix 4G since pre-release day, Feb 22nd of last year. Haven't had a single issue. Others who got theirs months later, or just recently, have had some issues that I dont know why they are having (Rescue Sqad Staff on a forum dedicated to the Atrix 4G and Atrix 2) Sometimes the only way to fix certain things are to replace the device.
Click to expand...
Click to collapse
Yeah that is what I'm probably going to do. But I still don't get why it works flawlessly with the stock BL...
Sent from my MB860 using XDA
same issue, everything like this.. i wonder when will we find a solution for this SOD problem?..
Im having the same issue with my atrix unlocked the BL / SOD, how can you return again to stock without hardbrick the phone? Thanks for the info in advance!
I'm having the same problem...
I'm wondering , maybe the ram fixes in the pudding topic could help solve this?
I have exactly the same issue. No SOD with stock rom 4.5.141 and face with SOD after unlocking bootloader. Anybody has any ideas?
Also getting SOD ...
I have exactly the same issue. No SOD with stock rom 4.5.141 and SOD after unlocking bootloader.
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Dasoccerguy said:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.
I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
Click to expand...
Click to collapse
Did you get it working then? Were you running A2 before hand?
Dasoccerguy said:
Hello everyone. I'm a noob.
I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.
I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.
In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.
Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.
At this point I just want a working phone again and I'm not sure what to do.
TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
Click to expand...
Click to collapse
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Simpsons11 said:
Did you get it working then? Were you running A2 before hand?
Click to expand...
Click to collapse
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
Lorenzo VonMatterhorn said:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.
there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .
you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.
THEN: (this is not in the OP for cm10 ) , perform THIS : http://forum.xda-developers.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .
i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
Click to expand...
Click to collapse
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Dasoccerguy said:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.
I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.
And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.
I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
Click to expand...
Click to collapse
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
http://www.youtube.com/watch?v=HJdvyufvYp0
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Lorenzo VonMatterhorn said:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.
watch this video. it may help.
youtubelink
the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)
sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.
2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:
if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.
i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
Click to expand...
Click to collapse
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Dasoccerguy said:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.
Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:
I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.
(haha... I couldn't quote you because of the outside link and my 'xda noob' status )
Click to expand...
Click to collapse
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Dasoccerguy said:
Success!
I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.
I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.
So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about . Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.
I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
Click to expand...
Click to collapse
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.
as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.
one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.
glad i could help! :highfive:
Dunno if I'm risking flaming but here goes...
Had my Rez from day one, the phone is HTC unlocked but S-ON. I am still running a stock, rooted and debloated GB rom (based on the very first OTA update we got way back when). The rom has run great for me and so I never really had much reason to update...
The ONLY persistent issue I've had is with 4G cutting out, usually whenever trying to watch vids on Youtube, or trying to use Google Maps. Works fine on 3G. Way back when, someone had posted a thread where a lot of people mentioned they were having this exact same issue, so I figured that it was not an issue with my particular phone or even the rom/firmware. Even non-Rezound Verizon customers were complaining that they were having the same issues at the time (early last summer) so it seemed to be a network issue.
Fast forward a year and no one seems to be complaining about this issue anymore, and my wife has a Galaxy S3 that does not exhibit the problem... so I'm assuming that one of the OTA's that bumped the Rez up to ICS and updated the radios/firmware fixed this issue as well, so I would like to finally update to the latest and hopefully be done with this issue.
I have been reading threads and I think I know what steps I need to take, and wanted to run it by you guys and make sure I'm not missing something or doing something I shouldn't be, and that I have them in the right order... so here's my understanding:
1. Make a nandroid and titanium backups
2. Backup everything on the internal and external SD card
3. Relock device
4. Do I need to flash back to the stock GB OTA (to restore stock bloat apps that I've removed) or can I go straight to next step??
5. Flash latest RUU (can I do this from a PH98IMG.zip or does it have to be an RUU.exe run from my computer? I strongly prefer the PH98IMG method if possible)
6. Unlock device
7. Flash recovery
8. Root device
I don't really have any interest in S-Off or any custom roms, so I have left those steps off. Even back with the Incredible and now with the Rez, I've always been happy with the stock Sense rom just with bloatware removed, and that's my end goal here as well. So, do I have everything covered?
Points 1 & 4
1. Use MyBackup root instead of Titanium.
4. It will do a complete wipe also in the process, not needed.
PH98IMG will work, I highly and strongly suggest contemplating s-off NOW(if you really want to, not needed) versus doing it after. The PH98IMG you might want to look at is 3.14.605.12. If it's of any help, there was a few OTA's on top of that, which VZW may ask if you want to take through an OTA on the Rez's rom.
cool thank you for the tips. I was able to get onto the latest global OTA and firmware without issue.