Was notified by ROM Manager that there was a new Recovery - 5.0.1.0. Let it load, and booted into recovery from ROM Manager. Nice blue menu pops up after briefly showing the box with yellow arrow (was afraid it was going to do a factory reset ...lol).
After shutting off device and pushing vol down/power, the NVflashed Recovery still pops up, so I am assuming the ROM manager Recovery is an updated "false flash" and does not replace the NVflashed one.
Yup.
10char
I've never uses bom manager so I would know.
Sent from my LG-P999 using xda premium
Funny story, I installed/Flashed the update 5.0.1.0 on a G2 I got off of CL. That blue text was weird.
I did the repartition of the SYSTEM/DATA and resized it to 575BM only way to flash Sense ROMS to the G2. I couldn't restore the NANDROID I made with 5.0.1.0 because 3.0.24 couldn't read.
So yeah, don't upgrade, cause your NANDROIDs might be incompatible. Of course this doesn't matter to us because the G2X uses different tool to create/FLASH NANDROIDS.
Are there Compatibility issues with NANDROIDs created on different versions? Just curious myself for the G2X
xsteven77x said:
I've never uses bom manager so I would know.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Just what is bom manager exactly anyway?
mr mystery said:
Just what is bom manager exactly anyway?
Click to expand...
Click to collapse
hahaha i think he meant ROM MANAGER lol
I didn't flash this via Rom Manager, but rather via the NVFlasher tool.
I think it is wonky some as the first boot was flashing and I couldn't go into the menu's via using the touch buttons or power/volume. A reboot fixed it but kinda wierd.
I like the blue. Change of pace from the yellow... and the Red was hard to see. Reminds me of the CyanogenMod Edition on the Nexus One.
gypsy214 said:
hahaha i think he meant ROM MANAGER lol
Click to expand...
Click to collapse
Pretty sure he meant BOM Manager, check the title of the thread
Just a joke.
Sent from my LG G2x
dude so what is this new bom manager i want to try!!
I figured "BOM Manager" was a play on "Bomb Manager", as in Rom manager is a bomb on the G2X since it can't do a real flash.
LordButtersI said:
I figured "BOM Manager" was a play on "Bomb Manager", as in Rom manager is a bomb on the G2X since it can't do a real flash.
Click to expand...
Click to collapse
LMFAO
Sent from my LG-P999 using xda premium
LordButtersI said:
I figured "BOM Manager" was a play on "Bomb Manager", as in Rom manager is a bomb on the G2X since it can't do a real flash.
Click to expand...
Click to collapse
It was.
I would not use it to create nandroids. if you can restore with it - fine. But the NVflashed Recovery is still the only way to reliability make and restore nandroids.
I am sure it will do things like clear cache and dalvek and flash zip files, and possibly download ROMs, but not much else on the G2X
Related
I need some help either getting root restored or getting CWM back. I rooted my G2X using the SuperOneClick method, did a nandroid backup of the original ROM, and then installed a CM7.1 nightly. After doing so, I found out that I no longer have root (or that the su binaries are corrupt) and there are a ton of issues with the currently CM7.1 nightly ROMs. I really just want to get back to the stock ROM that I have a nandroid of. When I do actually get to the Android Recovery screen, it sits at "Formatting MISC:..." and I can't select any other options (not sure what that's all about). I have tried rooting again, but I get errors saying things like "chmod: no such tool".
Does anyone know another way to get into CWM, know how to restore root, or have an alternative to restore a nandroid backup?
I had the same problem when updating from virtuous vision (froyo) to virtuous visioin unity. 2hat solved the issue for me was uninstalling SU and reinstalling it from the market.
Not shure if this'll solve it for you though.
Sent from my HTC Vision using XDA Premium App
Lord Mort said:
I had the same problem when updating from virtuous vision (froyo) to virtuous visioin unity. 2hat solved the issue for me was uninstalling SU and reinstalling it from the market.
Not shure if this'll solve it for you though.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Thanks, but I can't uninstall SU.
Bugger Have you tried reinstalling it from Market anyways?
Sent from my HTC Vision using XDA Premium App
Sage08 said:
Thanks, but I can't uninstall SU.
Click to expand...
Click to collapse
Grab titanium backup from the market, it'll let you uninstall it from system.
Sent from my HTC Glacier
He lost root. Can't remove system apps. Did you nvflash clockwork recovery??
Sent from my LG-P999 using XDA App
Smurphjw said:
He lost root. Can't remove system apps. Did you nvflash clockwork recovery??
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yup, nvflash CWM is your best bet at this point. Disregard the titanium suggestion.
Same exact thing happened to me. ROM Manager says I have CWM 3.0.2.7 current, but I can't reboot into recovery, restore any backups, fix permissions, etc. I noticed it when I tried to re-flash CM7 nightly #37 because my wifi was stuck at "obtaining IP address" and I was getting 3 or 4 force close notifications at startup. Installed root check and it said "root access is not properly configured or was not granted. SU binary not found in the system declared PATH."
Going to try nvflash CWM and go from there. Hoping to get this beast running proper!
downloaded pg asop p-999
i need help guys...Anyone. i was told to grab cynogen ,. phone was root, changed e over from stock perfectly but now when it reboots it keeps repeating the opening " X " screen. What do i do? please help
gathman81 said:
i need help guys...Anyone. i was told to grab cynogen ,. phone was root, changed e over from stock perfectly but now when it reboots it keeps repeating the opening " X " screen. What do i do? please help
Click to expand...
Click to collapse
Wipe it clean and reflash it.
gathman81 said:
i need help guys...Anyone. i was told to grab cynogen ,. phone was root, changed e over from stock perfectly but now when it reboots it keeps repeating the opening " X " screen. What do i do? please help
Click to expand...
Click to collapse
Opening X? Which rom did you flash? That's not CM7 ... maybe Faux's AOSP rom?
phburks said:
Opening X? Which rom did you flash? That's not CM7 ... maybe Faux's AOSP rom?
Click to expand...
Click to collapse
lol yea that aint cm thats gotta be fauxs, thats the colored nexus x
sarni84 said:
lol yea that aint cm thats gotta be fauxs, thats the colored nexus x
Click to expand...
Click to collapse
Exactly my thoughts.
phburks said:
Exactly my thoughts.
Click to expand...
Click to collapse
People just need to stop tinkering with their phone's software if they don't know what they're doing. They screw something up and come crying back here for help. Now, I know we were all 'noobs' at one point... But at least put the effort into reading up on details and be at least 90% certain you know what to do, before you eff anything up. Seriously guys. We can help, but you shouldn't be doing this sort of stuff if you aren't up for it yet!
I know all of us, the more seasoned geeks, have had multiple android devices so we know our way around. And we were in the same boat as you once too... Learning the basics and all that. But don't be flashing roms and/or kernels if you don't know what adb is. #justsaying.
Now, for your problem. I'm not even sure if you used NVFlash to flash a recovery. And if your getting weird errors while booting into recovery, flash it again. Once in recovery all you have to do is restore your back up, simple as that. There's no need to flash other roms. Now, if you used ROM Manager to flash your recovery... Then your nandroid is probably stored on your internal SD. And if you have an external SD recovery then you can't get at it. Maybe I missed something but I'm not sure if that's even the problem. But there is a stock/rooted nandroid here in the dev section, copy that to the proper location on your external SD and proceed to restore that.
Try that first before you flash anything, It seems most logical to me at least
I found these instructions on using nvflash to reflash CWM recovery (link below). It worked like a charm for me- but I had a backup from just after I rooted. After restoring it to original (rooted), I wiped and reflashed the latest CM7 nightly #61 with gapps. You can probably just flash the latest nightly instead of going back to original like I did.
http://forum.xda-developers.com/showthread.php?t=1054492&highlight=nvflash
Quick question guys... I was reading that cm7 RC 1 can be installed by only rooting your phone and then using rom manager. Is this true or are there other steps required? I know there used to be other things that needed to be done but maybe with the new RC is got easier?
Thanks for the help
Sent from my LG-P999 using XDA App
phantasybm said:
Quick question guys... I was reading that cm7 RC 1 can be installed by only rooting your phone and then using rom manager. Is this true or are there other steps required? I know there used to be other things that needed to be done but maybe with the new RC is got easier?
Thanks for the help
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Well, even though you could do it with only ROM manager and root it is highly recommended that you flash CWM recovery just in case anything goes bad you can always bring the recovery and reflash or restore.
Sent From My Stock G2x
^^^^^ agreed. The plain-jane method of rooting/RomManager/CWM works but if something happens where you can't get into RomManager (aka bootloop) then your SOL.
Do yourself a favor and spend 3 seconds and NVFlash. You only have to do it once and you will be forever able to save your skin if something goes bad.
Thanks guys.
So I root first (already done), NVFlash (done some reading but still not 100% sure what exactly this does or how to do it) and then set up cement recovery?
Sent from my LG-P999 using XDA App
I haven't used the rom manager app once on the g2x.
G2x with CM7 and faux kernel. NONSENSE!!!!
tackleberry said:
I haven't used the rom manager app once on the g2x.
G2x with CM7 and faux kernel. NONSENSE!!!!
Click to expand...
Click to collapse
me neither, lol and to the other guy nvflash u want because say your phone goes into a bootloop what u gonna do? u cant do nothing but pull battery out then when u turn your phone on it just keeps bootlooping not letting u into the phone ever, well thats what would happen if u got a bad download or flashed the wrong thing by accident , dude accidents do happen, rom manager is what they call a fake flash, ..........now nvflash really puts recovery on your phone it over writes your stock recovery, and if your going into a bootloop u can pull battery put back in then hold vol down and power and bingo your in recovery, it looks the same as rom managers recovery, but with this one u can actually get into it and if your bootlooping u would just restore a nandroid or reflash another rom and your good, ....kinda a failsafe i live by it and dont use rom manager , and if u want to see your backups and rename them use astro zip in market its free too
sarni84 said:
....kinda a failsafe i live by it and dont use rom manager,
Click to expand...
Click to collapse
That is all you need to know... NVflash is the only way to go if you absolutely want to be sure you can save your phone...
I don't know why people question that...
Sent from my butt using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1054492
How to setup and use NVflash.
Thanks for the heads up. I was just about to dive in with Rom Manager alone. REALLY don't need new problems.
According to Cyanogenmod's wiki you can flash recovery from ROM Manager, it says nothing about this NVFlash. I did this and rebooted into Clockwork and flashed CM7 RC1, and now I can't get back into Clockwork, just the default one, and ROM Manager can't execute anything, I can't connect to wifi and, I get various Force Close messages at start up. So is the wiki lying to me?
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App
jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It made a huge difference. Things are running much more smoothly now that I used nvflash and reinstalled CM7.1-RC1.
Awesome enjoy
Sent from my LG-P999 using XDA App
jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Click to expand...
Click to collapse
It's almost like people don't read the threads about rooting. Every one that I read said, in no uncertain terms, you NEED to use NVflash if you want permanent root....
Sent from my butt using XDA Premium App
The thing is there is incomplete information all over the place and it changes constantly, and it's difficult to keep up on what is needed or not. Cyanogen's wiki doesn't say it's needed, and I figured that meant the problems with ROM Manager and Clockwork had been resolved in the most recent versions.
jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Same **** I said in cm7 rrc thread. Yet I get laughed at and ridiculed.
U arr correct
Sent from my LG-P999 using Tapatalk
KeithLM said:
The thing is there is incomplete information all over the place and it changes constantly, and it's difficult to keep up on what is needed or not. Cyanogen's wiki doesn't say it's needed, and I figured that meant the problems with ROM Manager and Clockwork had been resolved in the most recent versions.
Click to expand...
Click to collapse
That's why I advocate, when in doubt, research some more. I didn't get the feeling that info was incomplete, everything I read said nvflash for permanent root and you can bet that the threads where people were asking for help because they were in a bootloop the first question asked was did you use nvflash... maybe cyanogen just figured that everyone already got recovery with nvflash, because you should have, and THEN it is safe to use RM...
Sent from my butt using XDA Premium App
Just installed CM7 as as update. Went thru the entire install process. Now stuck in a continous loop of the cool dude on the skateboard, the arrow circle, then black screen and starts all over again
Can someone help a brother out
mahgninnuc93 said:
Just installed CM7 as as update. Went thru the entire install process. Now stuck in a continous loop of the cool dude on the skateboard, the arrow circle, then black screen and starts all over again
Can someone help a brother out
Click to expand...
Click to collapse
Did you install NV flash? If you did so then simply press volume down and power until you see a list full of android apps and wipe factory/data, dalvick cache and battery wipe. Then reflash the rom. Most likely it was just a bad flash. If the rom still won't load then its also possible that the rom file never fully downloaded properly to your phone or computer.
Sent from my LG-P999 using XDA Premium App
Thanks, I will try again and let ya know what happened. I didnt do the wipes first. SO I"m thinking that may be the culprit. I"m new to the droid scene after a few years in Apple's iron fist of hell.
Did it again and still the same deal...GOnna try the nightly from yesterday.
mahgninnuc93 said:
Thanks, I will try again and let ya know what happened. I didnt do the wipes first. SO I"m thinking that may be the culprit. I"m new to the droid scene after a few years in Apple's iron fist of hell.
Did tit again and still the same deal...GOnna try the nightly from yesterday.
Click to expand...
Click to collapse
Welcome on board to android! I'm pretty sure its something that you might just be overlooking. I recommend watching a few YouTube videos to help you get a better understanding on what to do. Type in something like "how to flash a rom". With all androids the method of flashing a rom is pretty much universal. Rooting methods aren't though.
Sent from my LG-P999 using XDA Premium App
This is the second ROM I am putting on. I already did the "leaked" gingerbread. I have heard so much positive about the CM7 I figured I would check that out. Also heard about something called eaglesblood. Dont know how different that is from CM7. I"ll get it going on. Should I always wipe the dalvik and battery when installing a new rom?
Shoot it did the same thing. What the hell am I doing wrong. It wasnt this hard doing the leaked gingerbread one LMAO.
Download the ROM again (may have had a bad copy).
wipe the data, then the cache.. then go into advance, wipe the dalvik. push the rom. Then hit 'fix permissions' in the advance menu. reboot.
schmit said:
Download the ROM again (may have had a bad copy).
wipe the data, then the cache.. then go into advance, wipe the dalvik. push the rom. Then hit 'fix permissions' in the advance menu. reboot.
Click to expand...
Click to collapse
I'll give that a shot LOL. Didnt add the fix permissions in there. Have already re-downloaded the ROM. Guess I should just pony up and buy the premium Rom manager thing so I can do this OTA instead of computer to sd card blah blah blah. Thanks again for all of the help.
chances are, you'll want the gapps on there too. Latest is available here (at the top, the 20110613 version) - http://goo-inside.me/gapps/
You after you do the wipes, push the rom, then push the gapps right after, fix permissions, reboot.
schmit said:
chances are, you'll want the gapps on there too. Latest is available here (at the top, the 20110613 version) - http://goo-inside.me/gapps/
You after you do the wipes, push the rom, then push the gapps right after, fix permissions, reboot.
Click to expand...
Click to collapse
Do the gapps go on the SD card also as an update or what would I name that file?
mahgninnuc93 said:
Do the gapps go on the SD card also as an update or what would I name that file?
Click to expand...
Click to collapse
ya, the gapps file goes in the same place as the rom. There is not a need to rename the file, use the file just as it was downloaded - just like the rom. Just do all the wipes.. push the rom, push the gapps file, fix permissions, reboot.
goin to bed.. you'll get it this time..
IT's ALIVE.....IT'S ALIIIIVE....MANY Thanks to both of you. Now let's see how this rocks compared to stock.
Just in case other have the same problem, i always format system in the mount section, when going back to a gingerbread from froyo. just a thought.
Thanks Sabo. I will keep that in mind. So far this kicks the crap out of stock. Even my signal is better. I'm getting reception in parts of my house that I didn't before
Sent from my LG-P999 using XDA App
mahgninnuc93 said:
IT's ALIVE.....IT'S ALIIIIVE....MANY Thanks to both of you. Now let's see how this rocks compared to stock.
Click to expand...
Click to collapse
Your welcome. Glad you woke up the beast (G2x).
Sent from my LG-P999 using XDA Premium App
OuncE718 said:
Your welcome. Glad you woke up the beast (G2x).
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Wonder if I should add Faux's kernel or anything like that? Your thoughts?
mahgninnuc93 said:
Wonder if I should add Faux's kernel or anything like that? Your thoughts?
Click to expand...
Click to collapse
Faux kernels are great try it
That's what she said...
Suprah said:
Faux kernels are great try it
That's what she said...
Click to expand...
Click to collapse
I second this. One thing that Faux is most known for is the wonderful kernel's he/she produces.
Sent from my LG-P999 using XDA Premium App
So yeah, any time I install an app from the market or the Amazon store, Sense force closes. I'm rooted using stock ROM. Known issue, or more importantly, advice?
Sent from my myTouch_4G_Slide using XDA Premium App
Did you try fixing permissions inside rom manager? That normally fixes root related fc issues.
Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App
You're rooted and you don't have ROM Manager?
rorytmeadows said:
Hmm I'm not actually sure what you mean. ROM manager?
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
You are kidding right? Please say this is a joke?
AndroidBotx said:
You are kidding right? Please say this is a joke?
Click to expand...
Click to collapse
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)
Blue6IX said:
Why? I rarely use it, and have only installed it a few times but don't usually keep it installed.
Honestly it's not necessary, but does let you easily install a custom recovery in some situations. For an S-OFF device there are much easier and more convenient ways to do so.
For the first few months we had the device there was no official recovery and ROM Manager was dangerous to use (not so anymore)
Click to expand...
Click to collapse
Press "flash recovery" and grant Superuser permissions. Not that hard.
Delivered via candygram for Mr. Mongo.
Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App
rorytmeadows said:
Haha I didn't realize I was so far out of the loop! With my phones, I root to get access to system folders, system apps, and to run adfree. I don't flash ROMs at all and always keep stock ROM. If I saw "ROM manager" before, I probably brushed it off without thinking because I associated it with custom ROMs.
Sent from my myTouch_4G_Slide using XDA Premium App
Click to expand...
Click to collapse
ROM Manager also allows you to flash ClockworkMod recovery and fixes your apps permissions. Once we get AOSP on this phone, you'll see what's really available.
blackknightavalon said:
fixes your apps permissions
Click to expand...
Click to collapse
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.
AndroidBotx said:
That is 100% normal when using the bone stock rom. Thats why 95% of peeps who root use a custom rom.
Click to expand...
Click to collapse
Not only that - but i've noticed on the stock ROM every time I plug my phone into a computer without rebooting first it locks up and restarts - I have yet to have this happen on my ROM or any of the others I used before that.
Once you root the stock ROM, it just doesn't seem to work as well, and I had the restart issue before root was available for us with this device. At first I thought it was my computer doing it, but now with an older desktop in service it happens on that too, and other random computers I plug into that my friends own too...I dunno.
There is a lot to be said for running a custom ROM instead of the stock one, beyond all the little fixes and enhancements they bring.
...but, that's why we all work together here to constantly bring better software with more support for these devices all over XDA.
rorytmeadows said:
So, I ran the fix app permissions from the ROM Manager and that didn't change anything. I went to install something from the market and although I didn't get a FORCE CLOSE pop up message, I did notice the MyTouch splash coming back up reloading Sense once again...
:-(
I appreciate any help offered. Thanks,
Click to expand...
Click to collapse
When is the last time you cleared cache and dalvik-cache? That might help with some of your issues.
I wrote a flashable-zip package that will do just that if you don't want to do it manually, it does a wipe (not format) so is compatible with all 3 clockworkmod recoveries we have available, since 4.0.0.8 and 4.0.0.9 don't implement the format command correctly.
Blue6IX said:
Third one is: Blue6IX_C01_Wipe.zip
MD5: a8c57de781b2abfca2dfcdcae57d439c
This one will wipe the /cache partition and also wipe dalvik-cache. Use this one if you are having problems with specific apps, especially when changing to a different version of an already installed app.
Click to expand...
Click to collapse
Either manually doing it or flashing my script might help with your issues, or might have no effect.
The next time you boot after doing so the machine will have to rebuild both cache and dalvik-cache, so it will take a little longer to boot that first time and after it's done and has sat for 5 minutes or so you should reboot the machine again before using it, just to get everything worked out right.
Hope it helps!
Does anyone know why? Its done this since I first rooted and did my first back up.
Sent from my SCH-I535 using xda app-developers app
same here. i think thats just how CWM works.
ddurandSGS3 said:
same here. i think thats just how CWM works.
Click to expand...
Click to collapse
Hmmm. Its only ever done it on my s III. Never did it on my og evo or HTC sensation. Maybe its the version of cwm. Is there an updated one? I have version 6.0.1.2 I know there's a touch version but I heard it was buggy.
Sent from my SCH-I535 using xda app-developers app
There is a bug in the RTC software for this phone. Until that but gets fixed (would have to be by Samsung or VZW) this isnt going to change.
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
musclehead84 said:
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
Click to expand...
Click to collapse
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
i keep 2 renamed nandroids that i restore regularly and run them without any issues.
apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
U can rename them as long as u don't use special characters.
Sent from my SCH-I535 using xda premium
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's the first I've heard this. I have the latest cwm touch and wrong dates show. Actually I keep seeing people use RM and the recovery isn't flashing right.
Sent from my S3 running Eclipse 2.1
same me
Same me as well,:crying:
I thought that was normal since those numbers are no where near a type of date, I just rename it once booted into ROM.
Sent from my SCH-I535 using XDA Premium App
i suffering same issue too
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
This is not true. I dl'd my CWM thru RM and my dates are still wrong. Where do u get this stuff?
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's incorrect. The date issue is still there regardless of how it's flashed in. Some people have reported issues with restoring after renaming. Consensus seams to be if you keep the default cwm assigned name and add your own to the end of it without any spaces, any reported issues dissappear.
Boom! Jellybomb biatch!
annoying for sure. I just rename the moment I am done and booted back up.
TWRP date is also wrong but you can rename them anything you want at time backup. :laugh:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Seirÿu said:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Click to expand...
Click to collapse
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
prdog1 said:
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
Click to expand...
Click to collapse
I got to jump on that one of these days to see what all the fuss is about, I'm just loving cwm touch too much! I assume when changing, your existing nandroids will become useless, so would make sense to copy onto your cpu incase they are needed down the road...?
Boom! Jellybomb biatch!