Hello i just perm rooted my shift with a video instruction in the development area. I dont recall anywhere though any instructions about backing up wimax keys. Did I really just get rid of 4g capability permantley?
carnivalrejectq said:
Hello i just perm rooted my shift with a video instruction in the development area. I dont recall anywhere though any instructions about backing up wimax keys. Did I really just get rid of 4g capability permantley?
Click to expand...
Click to collapse
Does the wimax key checker written by joeykrim in the app market say your wimax keys are not present? If so and you haven't created a nandroid backup or backed them up manually, then yes you have lost your wimax capabilities.
If you haven't checked I suggest you do so, if you still have them I suggest making a backup.
Rooting doesn't delete your wimax keys. Its just a safety precaution. If you did everythibg right, you should still have it.
There's an app in the market that will confirm this for you. Its call wimax rsa key checker.
Once you've done that, get rom manager from the market, and install clockworkmod via rom manager. Then do a backup. This should backup your wimax keys.
i dont need a signature
thanks yall....there still there and are now backed up.....one other thing i am confused about though that maybe someone can answer....im new to toying with the shift , coming from an epic , if something gos wrong with a kernel or rom like a bad flash.....on the epic i would just start all over odining back to stock and re rooting if a flash wouldnt work with wipes.....what happenes with bad flashes on a permantley rooted shift?!? Or say what happens if you just simply wanna switch to another rom or kernel? Wouldnt having one already on there make it difficult?
carnivalrejectq said:
thanks yall....there still there and are now backed up.....one other thing i am confused about though that maybe someone can answer....im new to toying with the shift , coming from an epic , if something gos wrong with a kernel or rom like a bad flash.....on the epic i would just start all over odining back to stock and re rooting if a flash wouldnt work with wipes.....what happenes with bad flashes on a permantley rooted shift?!? Or say what happens if you just simply wanna switch to another rom or kernel? Wouldnt having one already on there make it difficult?
Click to expand...
Click to collapse
Before you do any major changes to your phone like flash a kernel or ROM you'll want to boot into recovery and make a backup. This is what they're referring to as a nandroid backup. It'll backup everything and if something goes wrong you just boot into recovery and restore the backup you so wisely made.
I'm from the Samsung Moment so this was new to me too. On the Moment it was the same process, clear all the way back to stock then reroot and reflash, etc etc. One of the many reasons HTC > Samsung.
^ Shift Faced
I see...so on the shift just having a nandroid backup makes you a ok in case of any problems?
From the most part, yes. As long as you can boot into recovery, you can restore your nandroid.
i dont need a signature
Related
Okay so I got a Droid 2 Global today and have been playing around with it, the first thing I noticed is a ton of bloatware. I have read a few guides, and though this is my 3rd android phone, I am still somewhat clueless at this stuff. After a bit of searching I managed to root with z4root, and got boostrap recovery and made a backup. Now I am seeing guides that say to freeze the apps with titanium backup, or move them somewhere else or this that or something else. However since I made a backup, does that mean I can just delete the files I don't like, and when an update comes out for my phone, use the backup to put them all back? This seems like the easiest solution to me, but I just want to make sure that would work as I don't know much about recovery things. Thanks for any help
ben7337 said:
. However since I made a backup, does that mean I can just delete the files I don't like, and when an update comes out for my phone, use the backup to put them all back? This seems like the easiest solution to me, but I just want to make sure that would work as I don't know much about recovery things. Thanks for any help
Click to expand...
Click to collapse
Yeah you can do that. The reason people were just freezing apps was due to the lack of an SBF for the D2G so if you delete and app and Verizon pushes an update you want you can't do it if you didn't back up your phone so now that there is an SBF you can delete them if you don't like them just don't delete until you know how to restore your phone with said SBF. That way if/when something goes south you are ahead of the learning curve instead of having to learn it all real quick so you can use your phone again.
newk8600 said:
Yeah you can do that. The reason people were just freezing apps was due to the lack of an SBF for the D2G so if you delete and app and Verizon pushes an update you want you can't do it if you didn't back up your phone so now that there is an SBF you can delete them if you don't like them just don't delete until you know how to restore your phone with said SBF. That way if/when something goes south you are ahead of the learning curve instead of having to learn it all real quick so you can use your phone again.
Click to expand...
Click to collapse
I don't think I'm following you. I made a backup with bootstrap, but bootstrap was out before the SBF was released, so are you saying that deleting the apps are fine, but my current boostrap backup will NOT restore the apps and I would need to restore with a old SBF that just came out? Also would it make a different that I am on the new 2.4.330 or something software version, but the SBF seems to be for the old 2.4.29 version?
If you mess up the phone bootstrap can't start. And you can't restore anything from it. It is not like the standard recovery which is independent from system image - it just hijacks normal boot to give you recovery where you can flash unsigned files. Or if you mess up and phone sits at M logo, custom recovery isn't going to help you. SBF is the only salvation.
It is fine to flash 2.4.29 over 2.4.330 updated phone. It has been confirmed multiple times to work fine. There is also word going about new SBF based on 2.4.330 that will be released in the following few days.
please be understanding, I'm asking for guidance not ridicule. I'm not used to the Samsung came from Dinc. need to know how i would create a backup before installing a rom? any help is welcome
My opinion is that Titanium Backup is a great tool if you think you may switch ROMs/phones a lot as you can select what to restore fairly easily. If you're on the Charge now, and are just going to install the Debloated ROM, you don't have to wipe data when flashing, so you shouldn't loose your settings and such.
Another vote for Titanium to back up apps and data.
Apparently CWM isn't working properly for nandroid restores, so we're kind of screwed there. The development section has a thread by imnuts on how to do dumps of the partitions on the phone to use to restore in Odin. Should work as a fallback if you can actually get Odin to work (I can't, Heimdall won't work for me either).
If you just want to back up all your Apps / Data / Pictures (not a ROM image), MyBackupRoot does a great job. I found the User Interface to be simpler than TiBackup.
Titanium Backup is a great app to have on your device.
imnuts said:
My opinion is that Titanium Backup is a great tool if you think you may switch ROMs/phones a lot as you can select what to restore fairly easily. If you're on the Charge now, and are just going to install the Debloated ROM, you don't have to wipe data when flashing, so you shouldn't loose your settings and such.
Click to expand...
Click to collapse
i forgot to mention i now have the CHARGE(rooted but on stock ED1) and coming from DINC. the ways of rooting and roming are different and if i may say confusing to me.
i read most of the threads in the Samsung Charge section, at this moment to tell you the truth i feel i should wait till things are clear (how to root & rom 4 dummies) up a bit.
what would you recommend?
spjetrovic said:
i forgot to mention i now have the CHARGE(rooted but on stock ED1) and coming from DINC. the ways of rooting and roming are different and if i may say confusing to me.
i read most of the threads in the Samsung Charge section, at this moment to tell you the truth i feel i should wait till things are clear (how to root & rom 4 dummies) up a bit.
what would you recommend?
Click to expand...
Click to collapse
IMO titainium backup is all you ever really need. It can backup all your data and apps and even be programed to do so on a schedule. Everything else can be flashed w/ CWM or odin. I never nandroid backup.
I am able to select make backup of current rom.
The samsung charge reboots into clockwork.
But there is no option to make a backup.
Just: reboot
install zip
clear cache
format internal sd
thats it.
WTF!
Its driving me crazy.
what do i need to do first.
I flashed cwr ok.
Lost!!!!!
He took backup off of cwr for now because it will brick your phone if you try to use it as of now.. He working on it trying to get it to work.. Thats what I'm waiting on also.. I like to have a full backup before playing.
Sent from my SCH-I510 using XDA App
CWM cannot be used to backup right now. It needs a serious fix from Kousch to work correctly.
If you think you really really need a full backup of your entire system all as one file, you can use the instructions here for using Odin to do this:
http://forum.xda-developers.com/showthread.php?t=1082288
However, most people will be better off using something like Titanium Backup.
Thank you!
Ok then who is He?
And where or when or how will i know when it will be ready?
Will it just say update in rom manager?
Or will i have to check out a forum topic?
Is there a link to this information you have posted?
thanks again, and happy rooting.
First, don't use the version from ROM Manager! Last I heard it would mess up your phone. Koush is the author of Clockwork Mod and ROM Manager.
Only way to know is to keep an eye out here for one of the devs to get a working version. imnuts has been reporting the problems to Koush, so he would likely be first to say anything.
You can search for information about it, but there's not a good singular point for this info.
Hi guys,
First of all I want to apologize with everybody here but I need help and I know that I might be drowning in a cup of water but right now I feel very frustrated because I can't find the answer to this...
ok, now I have a T-Mobile G2X, I was reading how to root, do backup, recovery, etc, and I was doing some research of how to go back to stock with all the t-mobile apps, so I went to a thread that was explaining that he had to use first clockworkmod before doing anything, so what I did was just plug my phone, activated the debug mode and click on a script file from the new version 4.x of clockworkmod, after that it messed up the phone started to force close apps, so I turned it off and back on, my surprise.... cycle reboot
now I cannot do anything with it, if I press the vol down button with the power it goes to a screen that says S/W upgrade Please wait while upgrading, I left it there hoping that it will come up soon
Can you guys help me??, I'm very frustrated
Thank you.
What had you actually done to your phone prior to clicking on the script? Had you already rooted it?
it was not rooted, i think that's why this happened, but i thought that wasnt needed since i was trying to do a backup BEFORE doing anything, ha stupid me
Did you try to do a factory reset by holding down the volume down and power button?
Sent from my LG-P999 using XDA Premium App
^ What tq745 said.
And then follow this guide word for word if you want to root/flash roms:
http://forum.xda-developers.com/showthread.php?t=1060715
I tried the factory reset and came a different screen but what I needed to do is to hold down the buttons for more time, now at least it boots
I still want to try the rooting, so let me have this clear, rooting the device doesn't delete any apps or config right? this is until you start messing with the roms and that.
thanks for the help guys!
yes rooting does not delete apps u do that yourself lol. it gives u superuser access, the ability to remove bloatware or freeze them (tmobiles apps) you can change the fonts, super cid, the ability to have another carrier on your phone if wanted, install custom roms and kernels, tether, and backup apps with titanium backup, which i suggest if u do root, awesome app and tool . basically u cant do this with a stock unrooted device.....also our super one click root is pretty simple just one click after u have lg's drivers installed, and its just as easy to unroot if u had too (like bringing it back to tmobile, warranty exchange).... to unroot its the same program just click on it and u will see unroot too.....pretty effin awesome...
wow now I understand it more, thanks for the explanation friend.
I'm following the tutorial that phburks posted, in there is the backup process, I hope everything goes perfect (fingers crossed)
thanks again!
The "script" was probably that NVFlash app that was created. Being improperly NVFlashed is why its stuck.
You need to remove the battery, hold both volume keys down while inserting the USB cable. Then follow the steps of NVFlashing.
Once you NVFlash and have a good clockworkmod setup, then you need to reset data, clear caches, and flash a good rom.
I'm getting ready to root my phone, but one thing I haven't been able to figure out is what is the best way to make an image of my stock rom on the AT&T Nexus S before using a tool that's going to delete all my data?
I would really like to make a full system image so that if anything goes wrong, I can flash it back to where it is before the root takes place. Is this possible? Is there a guide out there that I just haven't seen?
Thanks
VillainousVivi said:
I'm getting ready to root my phone, but one thing I haven't been able to figure out is what is the best way to make an image of my stock rom on the AT&T Nexus S before using a tool that's going to delete all my data?
I would really like to make a full system image so that if anything goes wrong, I can flash it back to where it is before the root takes place. Is this possible? Is there a guide out there that I just haven't seen?
Thanks
Click to expand...
Click to collapse
i hate saying this, but its true. this should go into the Q&A section, not into development. anyways, i think that you need root for that. but if there is a way, i think that it would be through adb.
Not a problem, if a mod can move it, that'd be great. I thought that a backup before making modifications would fall under the realm of development. After all, without a good backup, I wouldn't want to make too many changes
VillainousVivi said:
Not a problem, if a mod can move it, that'd be great. I thought that a backup before making modifications would fall under the realm of development. After all, without a good backup, I wouldn't want to make too many changes
Click to expand...
Click to collapse
what you want is to perform a nandroid backup, and you can do that through a custom recovery. you either need to unlock your bootloader for that(which wipes your phone and sd storage) or you can search how to root without unlocking the bootloader, root it, and use rom manager to flash a recovery/perform a nandroid backup without wiping but getting root.
Just use my back up pro to back up whatever that app will allow. Then copy over all your SDCard contents to your computer....Google takes care of contacts and apps....
Sent using two tin cans and some string.....
I've been sitting on my stock Rogers Infuse 4G since I got it, hoping that they would at the very least release an update to ICS. I've pretty much given up all hope, especially now since the Infuse was listed as one of the "violators" in the recent lawsuit. So, in giving up there, I've started to try and get up to speed with what's available in terms of custom ROMs for the Infuse, etc...
I previously had a Captivate (seems like I pick the wrong phones) and have kept that one stock as well (now my wife's phone) aside from the official 2.3.3 update Samsung came out with for it. I checked in here once in a while to try and keep track of some of the updates as I thought about going for a custom rom, but I never had the balls to try anything (I've only ever flashed one phone in my life, and it was bought 2nd hand for $20 ) since I actually *must have* a working phone due to having a kid (daycare calls are kind of important!). However checking today, it seems like I am totally out of the loop and I just don't have the time to try and wade through thousands of pages on various threads to find out what the current "ways" are and such... but I know what I want to achieve so I'm hoping you folks are nice enough to at the very least give me a "search you noob" and point me to some threads :silly:
Since I'm totally stock, from what I'm gathering I think I need (and really I more of need a complete checklist of things to do rather than a "do it for me" kind of thing) to do is:
1) jot down my modem and apn settings and such (already done)
2) back up everything i need, pop out sd card (know how to do this)
3) wipe/clear to factory default (... and this)
4) back up the current rom - everything in case I want to return back to exactly the way the phone is stock
5) figure out what i need to do to flash CWM or something so I have the necessary recovery mode options?
6) flash to ICS (since from what I gather, I need to do that if I want to go to JB)?
7) follow instructions I found on the unnoficial CM10 JB thread to flash to JB
?) flash a new kernel? (is this done already during a rom flash; are there any new kernels?)
As commented, I can figure out 1-3 since I'm not stupid, but I have no idea what is even needed to do 4, nor do I know exactly all the tiny, necessary, steps to do the rest after that... especially since reading some things it seems like most of this is for AT&T users and since I'm on Rogers with a I997R (I assume the R means Rogers), I don't want to mess up my modem or other things to prevent the phone working for me... and these are the steps I'm hoping people can help me with.
So far, in prep, I've noted my phone info (basically everything in Phone settings) and I can back up all my apps and such that I care about, and I've downloaded the unofficial CM10 JB download and the Google apps apk as well, and on the same thread was a link to a 1-click ICS flash or something... so I got that too. Since I want to end up with JB, I'm not too concerned (or should I be?) with it being AT&T stuff to get to ICS, since it's the JB flash that I'd really want to ensure works for me.
Is anyone willing to help me out? I really wish I didn't have to be the "next loser" to make a thread like this but I just haven't had the time to be able to keep up with all the info going around (voodoo mods and whatever else?!) to be able to make sense of all this myself!
Thank you!
This looks like a good place for you to start
http://forum.xda-developers.com/showthread.php?t=1197248&highlight=how+to+root+rogers
First thing to do of course is read, read, read. Understanding what you are doing and why you are doing it is the most valuable resource you can have.
The gist of it is though: to install the custom updated roms, you need root. For Rogers infuse users that is very easy to do; all you have to do is install a rooted kernel in odin. After you do that you make a nandroid (and/or EFS) backup, and install whatever rom you want. CM9 and CM10 have their own kernel, so don't worry about that.
adfurgerson posted the step-by-step guide above me, although the links in the OP may be down. I have the mirrors here: http://minus.com/moAvVibed/
the 3 files in there are:
Odin_Infused_Gingerbread_Kernel_v1.zip - This is the rooted kernel you are flashing
Odin_Stock_Rogers_UXKG3_Kernel.zip - This is the stock rogers unrooted kernel if you want to unroot and go COMPLETELY stock for whatever reason (I doubt you will ever need to use this tbh)
Odin_UXKG3_rooted_no_bootloaders_v2.zip - The stock Rogers FIRMWARE. If you ever mess up you use this to "start from scratch". You will still be rooted though if you don't use the stock kernel above.
So yeah, just flash the kernel in odin as described in the above thread and you will have root + cwm.
From there you reboot into cwm (turn off, turn on holding vol+ and vol- buttons) and make a nandroid backup of your stock rogers rom (or an EFS backup with the infuse toolkit: click here), flash CM9 as per the instructions in the OP, and finally CM10 as per the instructions in the OP.
Also remember:
1. The infuse is almost impossible to hard brick. The only real way to do so is to improperly flash bootloaders, which a rogers infuse user will never have to do. Only AT&T users coming from Froyo have to do it. So keep that in mind.
2. On the chance that you get soft-bricked (screen won't go past samsung logo for example) you can always go back to flashing the stock rom/rooted kernel again in odin and start all over again.
The only thing that I can add to Threi's excellent reply is to mention the one click to ICS. It is in the first post of Scott's CM10 thread,it should give you the ICS recovery that is needed to flash JB without flashing a full ICS ROM.
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
j.smith said:
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
Click to expand...
Click to collapse
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
adfurgerson said:
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
Click to expand...
Click to collapse
Aha, perfect description. I didn't realize I had to get a new kernel to have CWM... and I'm guessing because of signing and such, that a custom kernel (with CWM) is required in order to flash a non-signed rom, which is why you couldn't just do it on stock, right?
Ok, so now armed with that info that clears up a lot, I guess I have just one question left (which I can probably find the answer to with some searching). I have read what that voodoo lagfix is and is this something that is standard now on all kernels (because if it can cause issues, I'd rather just have a kernel without it)? Are there any "rooted" kernels without the lagfix built in so I don't have to remember about disabling the lagfix? ...or is there a way to install CWM on to my current kernel?
*edit* Ok, I realize I might be a bit too picky about the voodoo lagfix thing. I found two good threads on dealing with Rogers specifically, so I'll read over those (and suck it up about voodoo) and see how it goes. Since my vacation got unfortunately cancelled due to a sick kid, I have some time to experiment this weekend... hopefully ending up with JB on my phone!
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
adfurgerson said:
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
Click to expand...
Click to collapse
Yep, just flashed the rooted cwm kernel and performed a backup. I read somewhere that you can/should back up your efs in case you lose your imei... so I'm just going to quickly look in to that, then i wipe and do some flashes to jb... shouldn't take long hopefully!
Ok, I seem to be stuck at trying to get the one-click ICS install to work. I've got the EZUpdater package to ensure I have the right drivers, yet everything I try with the one-click seems to tell me that the drivers aren't installed and then launches an installer which also doesn't seem to detect the phone... yet EZUpdater will run fine, etc...
I'm just about to reboot and launch device driver in a mode to list all hidden/previously installed devices and nuke them from history to hopefully purge my system of all traces of any drivers and install EZUpdater one more time to get the drivers installed.
Any reason why my phone wouldn't show up in this one-click (it uses heimdall or whatever) program, but seems to work in most everything else (adb even runs fine)?
*edit*
Got it all working! I couldn't get the one-click ICS to work for the life of me... it just didn't see the drivers even though they were there and working. I guessed maybe it had to do with me running Windows 7 x64 and having x64 drivers, but the one-click maybe being 32bit. I even tried installing the x64 Java JRE but didn't seem to make any difference.
I ended up having to flash CM9 which worked fine, then going to CM10. Had no issues doing that... wish I had just tried that before since that one-click wasted hours of my day and got me somewhat frustrated!