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***
Related
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.
So here is my issue. I have a Droid X. Used EasyRoot to root before 2.2, once 2.2 came out i ditched easyroot, DLed 2.2 and then did the Droid2 Method of installing root. Since I finally got froyo (and figured Ginger woudlnt be out for awhile) i figured i would try my hands at adding some themes. I installed ROM Manager and Bootstrapper (both paid) and flashed clokworkmod and played around with them for a day or so, and kinda figured it wasnt really what i wanted to get into, and decided to go back to just plain root.
So i UNinstalled both root manager and Bootstrapper, and did a batt pull... Now everytime i do a batt pull the "clockwork recovery" screen comes up asking if i want to recover my device. Why is this still on the phone if i uninstalled ROM Manager? There is a folder in my files labeled "Clockwork" but im almost afraid now that if i delete it ill get a Bloop.
How do i go about getting clockwork off my phone? Also, with the Droid2 root method, if i just remove the root, will clockwork and everything else go with it? then i can just re-root?
Clockwork Recovery is seperate from ROM Manager.
ROM Manager can be used to control Clockwork Recovery, but it is NOT CR.
I don't own a DroidX, so I don't know if it's possible to get back to the stock recovery, but no matter what, you shouldn't have to worry about anything.
Clockwork should stay on your phone pretty much regardless of anything else. Even if you factory restore your phone, it'll still be there because it's your recovery partition.
Basically, think of it as that message on an HP/Dell/Others that says "Press F11 to enter recovery mode" and from there you can reinstall a factory refresh of windows.
Same thing here, except you'd restore a backup you've made previously.
You could also flash a ROM you've found online.
You could also initiate a factory reset, but if you've messed with anything in the /system directory, it might not work.
That makes sense. So I guess my next question is Ifi have to take the phone back to vzw will that flag it as voided? Even if I remove root? And will I have problems with any future OTAs?
Sent from my DROIDX using Tapatalk
Before you flame, I did read this and was still a bit confused.
Basically, I've been using my Verizon-ROM'd Charge (with the latest updates) for about a month now. I'm ready to ODIN over to a new ROM (probably the 8/3/11 HumbleComb ROM), but without a one-click root, I'm not sure how I can install/run/backup all my data with TB if I don't have root access.
So right now, I'm looking for any way to root my Charge, backup all the apps/data before I flash a ROM that seems (from my reading) to do a full wipe.
The other problem I'm having is in regards to my wife's Charge. We both came from Vibrants and she had quite a few important apps (with critical data) she'd like to bring over. However, she could care less about going to a rooted/aftermarket ROM. She just wants her old apps to work.
I've searched fellas... I'd really like some help on this. Please throw me a line... even if it's a link to a thread I missed.
Thanks in advance.
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Nevermind...
mbh87 said:
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Click to expand...
Click to collapse
Awesome! I'll give it a try and see how it goes. I appreciate the helps.
**EDIT**
That worked perfectly. Thanks! Backing up everything with TB now in preparation for flash a real ROM.
Mods, please move as necessary.
most roms nowadays will root you when flashed/odined so yeah just back everything up and load up the rom of your choice
blazing through on my VZ Droid Charge 4G
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Flapjack said:
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Click to expand...
Click to collapse
Wipe everything in recovery (data/cache/dalvik) and then plug into Odin and flash. That works every time for me when it sticks on the Samsung logo...
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.
Hey,
So I was a victim of not enough reading and doing to much at one.
I had a rooted stock GB ROM on my D2G and through easy enough, BootStrap, CWM via Rom Manager and flash CM 7.1. All should be good.
WRONG
I got hung up at the red M logo and try various things to revert to stock b/c there was no way I was getting into the CWM recovery console again.
After failing at every corner a random and 10,000th battery pull I ended up in CWM.
Since the one thing I did right was a nandroid backup I was restored it and the phone booted. I then shut down, dropped in SIM (rogers) and booted back up.
Now everytime I reboot it takes me to CWM. Forcing me to hit reboot system now otherwise it sits in recovery.
Any way to have it not boot into recovery? Just boot normal?
Thanks.
First, if you are on Rogers in Canada - do not bother trying CM7 - doesn't work properly on GSM. Stock firmware will be much more useful.
Second - There are two CM7's (if you are determined to try it) - one is Froyo base (the one found on CyanogenMod site) and the other one is GB base. It seems you flashed the Froyo based one on top of Gingerbread thus you ended up stuck on red M logo. To fix the problem - you have to either try flashing GB base CM7 from CWM or (better) SBF and start over. Again - if you want Froyo based CM - use the 2.4.29/2.4.33 SBF. If you want to try the Gingerbread based one (check rootzwiki for more info), flash the GB SBF that was recently made available or flash 2.4.29/330 and OTA to 4.5.608. Root, CWM and so and so. But pick your CM7 package carefully!
But if you are not on CDMA - you better don't waste your time with CM7.
Thanks for the reply. The phone boots fine now.
One question tho.
I have some how lost the Accounts and Sync Option.
If I do a factory reset (from phone settings not recovery mode)will I loose root and will I loose the Gingerbread OTA update that was done on the phone before I got it?
Or do you know how to recover something like Accounts and Sync?
I am going to be sticking with the Stock ROM
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
leobg said:
Have you disabled any system apps? This could be a reason for broken accounts.
As far as factory reset, either from phone menu or from recovery, will not remove root or any other changes you might have made in /system. It simply deletes /data partition.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks I discovered that I had deleted the "Setup.apk" without backing up.
Retrieved that app from another member and all is well.