Related
So, I've tried following the directions for the "nearly" one-step root, and the process completes, but I get no response when I run the Super app, just a blank screen. Is that normal?
Also, from what I've been able to find, it appears there are no released SBF's for the R2D2, so if I brick my phone, I'm SOL. I don't want to end up with a non-warranted paper-weight, so for now I unrooted it....however...did I do something wrong, and if so can someone fill me in?
Thanks!
which one step? I used the Z4root and had zero issues. Rooted within a minute.
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
osufans said:
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
Click to expand...
Click to collapse
Super user app is blank until root apps are used.
For now I wouldn't use a ROM manager you need Koush's Bootstrap to be able to do a backup. It's on the market. To use it just tap the Bootstrap button then wait for the success toast (box) and then tap Reboot Recovery and your phone will boot into Clockwork mod. Backup will take an img of the phone as it is at the point where you backed up. To restore if you mess something on a later install but if you can't get into clockwork for some reason you might be out of luck. Because there is no SBF specifically available for the R2D2 D2 but I've heard that the 2.3.20 might unbrick bricked R2D2's but you won' have the same verizon version you have now it'll be a step back.
OK. I do have bootstrap recovery installed and was able to perform a backup.
Also found a link to some of the bloatware you can "safely" remove. I'm still tweaking it....but that being said, what else can you do (i.e. - overclock, etc.)?
You can overclock, install libs and bins that access hardware features locked out by vzw, change roms and themes....yada, yada.....the 2.3.20 sbf is not a step back. The radio update and kernel tweaks for battery life are not in the 2.4.5 system. They had the rom version because some files are different between the two.
Sent from my DROID2 using XDA App
I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything
download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
couldn't agree more. i rooted my phone the other day with a kernel change, but now i want to isntall a rom but cant even start to work out the way to get cwm on to flash a rom!!! annoyinh to say the least.... the x10 and sgs1 i had were a breeze
da.trute said:
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
Click to expand...
Click to collapse
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Freedom to choose is a great thing. I like having options.
pulser_g2 said:
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Click to expand...
Click to collapse
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Intratech said:
Freedom to choose is a great thing. I like having options.
Click to expand...
Click to collapse
It is yes, however you seem to have misunderstood the thread, having different methods being forced up you by different cooks is not choice, choice would be that all methods were compatible and interchangeable, they are not apparently. Some require different roots / kernels.
EDIT. not suggesting anything is really being forced on us, I appreciate all dev work, just hoping for a bit more conformity of installation process.
da.trute said:
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Click to expand...
Click to collapse
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
seshmaru said:
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
Click to expand...
Click to collapse
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
da.trute said:
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
Click to expand...
Click to collapse
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Wow. He's just asking a question. Why belittle people for asking?
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Because I see exactly 3 threads on the same page that could either answer his question or link him to the answer. But people are too lazy to read.
Due to people like this we have a thread here which isn't needed at all since there is conformity to flashing across all ROMs. All because people make claims about things when they don't even know how it works.
The big difference in swapping from one custom rom to another is not the method of flashing but do you need a clean phone to install a custom rom on top of another one .
My personal choice is a fully wiped phone before installing a new custom rom .
Methods CWM or Odin mostly CWM as thats the major choice for devs .Kies is not a rom flash tool .
Choice also gives a better recovery option .
Villain on top of or below Cognition both use same flash method via rooted CWM flash .
The problem on this forum is not three or four choices but a complete refusal by many to even bother reading any instructions .
jje
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Hi, you get used to these ***** after a while
seshmaru said:
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Click to expand...
Click to collapse
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
da.trute said:
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
Click to expand...
Click to collapse
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
seshmaru said:
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
Click to expand...
Click to collapse
what does this actually mean then?
"Make sure you got CF Root CWM (not the clockworkmod root)"
I have flashed all three roms using the exact same method .
Changed kernels four times this week using CWM .
Revived one bricked phone using Odin .
jje
Hollow.Droid said:
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
Click to expand...
Click to collapse
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
da.trute said:
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
Click to expand...
Click to collapse
No, there is only 1 method for ROM flashing, CWM. Every ROM has CWM, CWM is the end all be all for you, no matter what different apps do, they all use 1 method CWM. CWM CWM CWM. Stop being dense and read up before posting dumb factually wrong claims.
Every single ROM can be flashed by holding volume up, center button and power, how difficult is it to grasp this concept?
Here this video should help you.
http://www.youtube.com/watch?v=JmvCpR45LKA
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
fixed it
I unplugged the battery and did a factory reset/format in ClockWorkMod. I rebooted and all seems well so far.
20 minutes is a looong time for Cyclonic to boot. Is it still working ok? As far as CW goes, I only use Rom Manager to downlod what I want/need. When it comes to flashing I wipe everything manually and flash from recovery. I don't trust the app. But thats me.
Sent from my PG06100 using xda premium
+1 to that. I always use the same Method for Flashing Roms ( The one linked in my Sig ) . Clear everything Manually. I try to never deviate from that. Reason being, after Flashing literally hundreds of times I've found it to be the most reliable way to Flash a Rom. Meaning the least amount of possibilities for issues later on down the road .
alarmpro said:
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
Click to expand...
Click to collapse
Flash newsense.
And don't forget to wipe dalvik.
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
jdjohn said:
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
Click to expand...
Click to collapse
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Did you get this sorted?
bilgerryan said:
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Click to expand...
Click to collapse
Chad The Pathfinder said:
Did you get this sorted?
Click to expand...
Click to collapse
No, still having trouble. I have flashed ClockworkMod Recovery (version 5.0.2.0) in the ROM Manager app, but when I 'reboot into recovery' within the app, it goes to the Android System Recovery. I'm also confused about the 'apply sdcard:update.zip' option in ASR...seems like that would update something if the file was set up properly.
I guess I need to search for a tutorial on how ASR and HBOOT work. Sorry to bother you guys with the basics.
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
bilgerryan said:
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
Click to expand...
Click to collapse
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
The only thing I use Rom Manager for is to get the recovery. The way I go into recovery is to turn my shift completely off (do a battery pull to make sure its completely off) then hold the volume down and power buttons at the same time until the bootloader screen comes on. (While there see if it says S-off near the top) then using the volume buttons highlight the recovery option and push the power button. Then when you're there use the volume buttons to navigate through the various fields and hit enter to select. I hope this is helpful to you. Good luck!
Edit: by the way, when you first get to the bootloader screen, it will automaticly do a check showing a few green lines. Thats ok. Just wait until its finnished then go into recovery the way I stated.
jdjohn said:
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
Click to expand...
Click to collapse
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
CNexus said:
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Was thinking that myself. Will have to wait til I get back, though...headed out of town. Thanks guys!
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Hmm, never mind then, it seemed as if your bootloader was still locked if the recovery wouldnt flash
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Yeah, just do what bilgerryan said (make sure that you download the one that says "flash through bootloader" or something along those lines)
Before flashing, download some md5sum tool and make sure it matches the one given on there
Sent from my PG06100 using xda premium
Finally got back to this and was able to install and use Dread's CW-Enhanced. So far I have only flashed the Speedy Rooted OTA 2.77.651.8 (bascially 2.3.4 rooted). GB had some features I was wanting, but missing, after rooting back to Froyo.
But before continuing on to other ROMs, I was wondering how you guys handle restoring basic apps and data each time you flash a new ROM. Or, do you only use extra play phones for new ROMs and not your daily user? It would seem that every time you flash, you need to restore SuperUser, Titanium, ROM Manager (ClockworkMod, then probably Dread's enhanced image file), Terminal Emulator, etc. And of course contacts and messaging history and other stuff like that.
So far, after flashing a ROM, I usually download Titanium (or MyBackup) and restore apps and data from backups before continuing. Do you just keep certain APK files on your SD card and install from ADB instead of re-downloading from Google Play Store each time?
I flash ROMs on my dd. Usually when I falsh a new ROM (not a nandroid) I fresh install my apps through the play store. Especially if switching between GB, ICS and JB! Some apps work well if carried over by tb but not all. You'll just have to experiment to see what works with your shift and what doesn't.
Also, the recovery only ever needs to be flashed once
What I used to do is backup my current rom with all my data and settings and then wipe + flash a new rom. If i liked it, then I would move my full box of apps and data to the new rom, but restoring data can go wonky so I always made a backup before doing that too. If i didnt like it, I would either restore my original backup for a bit or keep flashing new roms until I either found one I liked or got tired and restored my backup lol
Hey guys I'm new to Android in general so sorry if these seem like dumb questions. I've searched online for a while now and I can't really seem to get a concrete answer. Anyways so I got CWM 5.5.0.4 running on my 7510 just fine last night. I then did a backup of everything from within CWM 5.5.0.4. Then I went and flashed CM10 Jellybean to see if it worked fine. Went back to CWM and tried restoring back to ICS, to check that too and it worked fine. I want to mention at this point I couldn't get Titanium Backup or ROM Manager working from withint ICS at this point because it kept saying that it couldn't get root access (I rooted my 7510 through the method listed as a guide in the Developers section of this forum), but since I could restore back without a problem to ICS with all my settings intact, I thought I'd give it a try anyways.
I then flashed back to CM10, and upgraded to the newest CWM Touch version 5.8.x.x from within ROM Manager once in CM10. I then decided I wanted to go back to ICS so I tried to restore back to ICS through CWM Touch, and it didn't work. I’ve tried doing an entire normal backup, and then strictly the apps, nothing works. Keeps telling me there’s an error.
What’s the best thing to do? Switch back to 5.5.0.4? Can I do that without turning on USB debug mode? Because I didn’t check this beforehand but I can’t click on Storage in settings and even access USB period, whether it’s to transfer stuff or to turn on USB Debug mode.
Any help would be appreciated! I mainly want to go back because all my apps are setup the way I like in ICS. Unless someone knows away to restore apps properly back without going through CWM, maybe through some app that can read the backup data if that makes any sense?
HeyYoWL said:
Hey guys I'm new to Android in general so sorry if these seem like dumb questions. I've searched online for a while now and I can't really seem to get a concrete answer. Anyways so I got CWM 5.5.0.4 running on my 7510 just fine last night. I then did a backup of everything from within CWM 5.5.0.4. Then I went and flashed CM10 Jellybean to see if it worked fine. Went back to CWM and tried restoring back to ICS, to check that too and it worked fine. I want to mention at this point I couldn't get Titanium Backup or ROM Manager working from withint ICS at this point because it kept saying that it couldn't get root access (I rooted my 7510 through the method listed as a guide in the Developers section of this forum), but since I could restore back without a problem to ICS with all my settings intact, I thought I'd give it a try anyways.
I then flashed back to CM10, and upgraded to the newest CWM Touch version 5.8.x.x from within ROM Manager once in CM10. I then decided I wanted to go back to ICS so I tried to restore back to ICS through CWM Touch, and it didn't work. I’ve tried doing an entire normal backup, and then strictly the apps, nothing works. Keeps telling me there’s an error.
What’s the best thing to do? Switch back to 5.5.0.4? Can I do that without turning on USB debug mode? Because I didn’t check this beforehand but I can’t click on Storage in settings and even access USB period, whether it’s to transfer stuff or to turn on USB Debug mode.
Any help would be appreciated! I mainly want to go back because all my apps are setup the way I like in ICS. Unless someone knows away to restore apps properly back without going through CWM, maybe through some app that can read the backup data if that makes any sense?
Click to expand...
Click to collapse
Easiest way is to go back to the old cwm. The touch ver is a bit uggly according to me. (Personly i run Twrp tocuh recovery. Its nice and sleek. Gives option to compress backupps to. Includes a filemanager to. )
Otherwise if you install clock work mod from gogle play there is an option to restore apps from the backup.
Sent from my GT-P7500, JellyBean rom v6, A1 kernel v1.7 using XDA Premium HD
How exactly do I go back to the old CWM? Do I have to enable USB Debugging mode? As I mentioned I can't even do that because it's greyed out for me in CM10.
I dont know why usb debug is incheckable, i'm not a dev. But don't think it's important if you flash cwm via odin.
Use the same method you got cwm the first time.
Easiest is flashing it through odin. I guess you can follow that root guide you used initialy.
Rom manager can restore apps from backupfile. Just go deeper in menus.
Sent from my GT-P7500, JellyBean rom v6, A1 kernel v1.7 using XDA Premium HD