Related
I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.
I am novice when it comes to flashing, rooting, SBFing, etc. I spent endless hours trying to figure out how to get my rooted VZ Froyo to GB. Finally I found a great download that allowed me to boot from a CD on my computer and flash the SBF back to my phone. It worked great I didn't even have to wipe the cache. The phone updated and GB was running. I got it rooted and thought all was going well. Now the only reason I root is to run wireless tether, here is where things went awry.
I find out that it is a big hassle to get tethering to work on GB, thanks Google. So i decide to try and revert back to Froyo. I use the same CD method that worked before, but this time it gets stuck in boot loop. Now I have to wipe the cache and lose all my settings and apps. Finally I get it all back together, minus many apps, I will have to remember them as I go along and re install them. All is all a serious pain in my ass, but a good learning experience.
Now, I wanted to ask a question about Bootstrapper backups. After the SBF and wipe, I rooted again and added Bootstrapper. Then I noticed that some of my backups where still there, (presumable on the SD card). So I tried to load on but it didn't work and the phone got stuck on the Moto icon boot. At this point I thought I had bricked it, but was able to do the CD SBF thing again and just start from scratch. Would there be anyway I could restore one of my backups successfully.
Use Advanced recovery and only restore /data.
Can you tell me what application you used for installing GB? Mine won't update and I don't care that much about tethering.
There's no “application” like that. There's OTA update that can be installed either automatically or via the stock Recovery. You must have your /system FS intact, however. z4root is OK, Droid 2 Bootstrap Recovery isn't. Removing CWM was discussed multiple times, google for “logwrapper.bin” or something like that.
#1 a backup from gb won't work with froyo & vice versa.
#2 tethering is NOT a problem on gb. (After rooting) Just use "open garden" free in market.
#3 I think I know which cd program you are using, it does not install the official ota but a rooted leak (I could be wrong)
There are guides on how to sbf (reset to factory out of box).
And there are guides on rooting and roming
---Here is one ---> http://rootzwiki.com/index.php?/topic/4922-CM7-for-Droid2-Global-User's-Thread#entry113470
Remember, read,read,read... know how to sbf and have a plan for when things DO go wrong.
Droid2 Global CM4D2G-GB-20111217 ***CM7 RevNumbers Kang***
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
I've had quite an ordeal with my G2X the past few days, and nothing is making sense. I was running CM 7.2 on the 2011 baseband but was getting frustrated with the excrutiatingly slow GPS lock. I read that the 2012 baseband has much faster locking, so I read up on and upgraded my baseband.
So then I had the stock V21y ROM and I rooted and installed ROM Manager, and then flashed CWM. After many, many attempts at getting back to my original config:
Holding down power and vol down just performs a factory reset, it does not start CWM. The only way I can get into CWM is via ROM Manager > Reboot into Recovery. Doesn't matter how many times I flash CWM recovery. This is CWM 5.0.2.0 installed from the Play store.
I cannot restore backups I made with my previous version of CWM. Always results in an error, "Can't mount /system".
I often can't even restore backups made with *this* version of CWM, also resulting in the above error.
I *can* restore some backups I made of the stock ROM, which *isn't* supposed to be possible. From what I read, trying this should result in the above error, "Can't mount /system", but I've never received that error backing up a stock rom.
Attempting to install CM 7.2 from scratch via CWM makes the device unbootable. Boot stops at the second LG boot screen (the wavy LG logo). And since I can't start CWM via power + vol down, I need to flash V21e over USB, root, install CWM, then restore my last saved V21y CWM backup, which is a huge pain.
So, can anyone explain what's going on here? I seem to be able to do things I shouldn't be able to do, and not do things I should be able to do, and CWM doesn't work like it used to or like it should.
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
ROM manager is fatal for this phone. It almost every time screws the flashing of a ROM or a restore.
Sent from my LG-P999
cricketAC said:
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
ROM manager is fatal for this phone. It almost every time screws the flashing of a ROM or a restore.
Sent from my LG-P999
Click to expand...
Click to collapse
NVFlash CWM 5.0.2.0
Sent from my LG-P999 using Tapatalk 2
cricketAC said:
Before anything,nvflash cwm on to your phone. If you were able to search and upgrade your base Band. This will be trivial.
Click to expand...
Click to collapse
You are absolutely correct. I totally forgot that this is how I went about it last time. I was able to restore my previous CM7.2 backups after I nvflashed CWM. Thank you both!
Well I can't say that I'm all that impressed with the new baseband. GPS doesn't seem to lock any faster. If anything it seems worse.
CM 7.2 didn't work out of the box either for calls. I had to install a manual update, and receiving calls are still more finicky than they used to be. Sometimes I don't receive calls, or pick up and the audio is garbled.
I also still have a phone freezing issue where messages received at night while the phone is charging almost always lock up the phone's screen. I had read somewhere here that this issue was resolve with the update, or at least less severe, but that isn't the case at all.
Whether these are new baseband issues, or just issues which wouldn't exist if I were just on a stock ROM isn't clear. I may just try stock for awhlie and see.