So I'm coming from Synergy Nightlies 73. Using TWRP2.2 I did the normal steps before loading a new ROM. ( Cache Wipe, Dalvik Wipe, System Wipe) Once I flashed the JellyWiz Beta 4 ROM the phone booted up just fine. However, it froze within a matter of seconds and I had no functionality. I pulled the battery a few times and each time the phone would freeze. I had to restore my previous ROM. Any ideas or has anyone had this problem? I really want to try out the new JellyWiz.
topd823 said:
So I'm coming from Synergy Nightlies 73. Using TWRP2.2 I did the normal steps before loading a new ROM. ( Cache Wipe, Dalvik Wipe, System Wipe) Once I flashed the JellyWiz Beta 4 ROM the phone booted up just fine. However, it froze within a matter of seconds and I had no functionality. I pulled the battery a few times and each time the phone would freeze. I had to restore my previous ROM. Any ideas or has anyone had this problem? I really want to try out the new JellyWiz.
Click to expand...
Click to collapse
try formatting system.
tu3218 said:
try formatting system.
Click to expand...
Click to collapse
1+
with cwm, it would be under mount and storage>format system/data/cache.
I don't use twrp but I'd think there's a similar option.
Also check md5 to make sure you have a good download.
Sent from a SYNERGIZED GalaxySIII
tu3218 said:
try formatting system.
Click to expand...
Click to collapse
I don't see that option(format system) anywhere. I went under wipe and wiped Cache, Dalvik, and System. I did try to select the Format Data but that option failed multiple times.
epagib said:
1+
with cwm, it would be under mount and storage>format system/data/cache.
Idont use twrp but I'd think there's a similar option
Also check md5 to make sure you have a good download.
Sent from a SYNERGIZED GalaxySIII
Click to expand...
Click to collapse
I've always used CWM without any problems until recently. It wasn't creating back up of my ROM. So I made the switch to TWRP which seems to work fine when loading other Synergy builds. I checked the MD5 and it was good. I may have to go back to CWM however, without a back up I'm afraid to flash anything.
topd823 said:
I've always used CWM without any problems until recently. It wasn't creating back up of my ROM. So I made the switch to TWRP which seems to work fine when loading other Synergy builds. I checked the MD5 and it was good. I may have to go back to CWM however, without a back up I'm afraid to flash anything.
Click to expand...
Click to collapse
Yeah, know what you mean about not having a backup. It always a hassel installing everything from scratch.
Have been using cwm 6012. Never had a problem making backups....or anything else.
But yes I'd try the system format along with clean wipe before installing Incubus beta4. I'm testing it right now too. Has few minor bugs, but overall very fast and slick
Sent from a SYNERGIZED GalaxySIII
epagib said:
Yeah, know what you mean about not having a backup. It always a hassel installing everything from scratch.
Have been using cwm 6012. Never had a problem making backups....or anything else.
But yes I'd try the system format along with clean wipe before installing Incubus beta4. I'm testing it right now too. Has few minor bugs, but overall very fast and slick
Sent from a SYNERGIZED GalaxySIII
Click to expand...
Click to collapse
So I went back to CWM Touch 5.8.4.9 everything worked like a charm. I was able to back up and install Incubus Beta 4. When I was using CWM I realized when you wipe data it says factory reset. Which is an option on TWRP in the wipe menu. So I believe that's what I was doing wrong. Operator error! Thanks for the the replies.
I haven't been able to get wifi tether to work on Beta 4. I'm going to search the forums for the solution. Just wondering if you've had an issue?
Related
Strange problem on my wife's Charge. I just got her rooted, onto GB EP1W, and put her on TeamSBrissenMod's ROM, which I have been happily running for days.
After flashing last night, I let her spend this morning restoring her apps, wallpapers, themes, etc. She likes pink, lol. Well, after all of that, when she was done and satisfied, I showed her how to access CWM and create a backup. She did it, but when she rebooted, the phone has reset itself back to the point where it would look like the ROM was just freshly installed. No apps, no nothing, right back down to the default ROM wallpaper.
I tried to go back and restore the backup she just created, but its just the same thing, vanilla, freshly installed ROM. Im at a loss, never seen this happen before, and she certainly didn't make a mistake and reset anything as she backed up.
Sent from my SCH-I510 using Tapatalk
And no i didnt flash some odd CWM from ROM Manager or anything strange. Used the (imnuts?) fixed recovery dated 8/17
Sent from my SCH-I510 using Tapatalk
unfortunately this is a known issue that CWM wipes data on first boot into it after installing the rom... same issue that was happening with earlier Gummy GB versions
Sent from my SCH-I510 using XDA App
This is a known issue with the Infinity ROM. Specifically, it is with the kernel that ships with the ext4 version of the ROM. imoseyon's kernel does not have this issue, and it is fully compatible with the ROM.
Ok two answers, and I appreciate both, but which is it? An issue with the kernel, or this version of CWM? If its CWM, that makes me not want to boot into CWM ever..how do i resolve/get around it? I was intending on doing my own backup today as a matter of fact. Now, not so sure lol. I'll go back to the ROM thread too to see who has had the issue previously.
Sent from my SCH-I510 using Tapatalk
Well the answer seems to be to avoid CWM while on Infinity. Guys have tried every CWM version there is and data wipes on each one.
Is there expected "official" support from Clockworkmod on it's way for the Charge?
Sent from my SCH-I510 using Tapatalk
richm052569 said:
Well the answer seems to be to avoid CWM while on Infinity. Guys have tried every CWM version there is and data wipes on each one.
Is there expected "official" support from Clockworkmod on it's way for the Charge?
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
The wipe has *nothing* to do with CWM. It has everything to do with the kernel. imnuts has said this. imoseyon's kernel does not cause wipes on any version of CWM. This is 100% verified.
Here's the link if you want it: http://rootzwiki.com/showthread.php...n-kernel-(stock-repacked-v2.3.2voodoo-9-28-11)
shrike1978 said:
The wipe has *nothing* to do with CWM. It has everything to do with the kernel. imnuts has said this. imoseyon's kernel does not cause wipes on any version of CWM. This is 100% verified.
Here's the link if you want it: http://rootzwiki.com/showthread.php...n-kernel-(stock-repacked-v2.3.2voodoo-9-28-11)
Click to expand...
Click to collapse
also (for myself anyway) it is only wiping data on the first boot into CWM... I flashed the Infinity rom, discovered it wasn't rooted so I booted into CWM and flashed superuser then booted up and was wiped but rooted, after that I've had no wipes
anoninja118 said:
also (for myself anyway) it is only wiping data on the first boot into CWM... I flashed the Infinity rom, discovered it wasn't rooted so I booted into CWM and flashed superuser then booted up and was wiped but rooted, after that I've had no wipes
Click to expand...
Click to collapse
I will second what shrike is saying. I have also started using imoseyon's kernel and have had no problems going into CWM for any installs since using them.
The reason your data is getting wiped only on the first time is because two of the EXT4 partitions (I think they're Cache and Data) get reformatted back to RFS by the kernel (after you reboot). This is what wipes your phone. The second time you go into CWM and reboot, those partitions are already RFS, so the kernel doesn't have to reformat them, and your data stays.
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Not needed if you use a sacrificial lamb and do the aztec dance...
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1365158
Super wipe is overkill and not needed . Most recoverys work great to wipe and flash any rom fine.
-XDA MODERATOR-
ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Wiping storage ain't like wiping your ass, 1 wipe suffices.
Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?
Oh, one final question - have you guys ever in CWM hit 'format sdcard' to fine that once you boot up and browse your SD card the format didn't work?
Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same here.......
10....0011....10101
ac17 said:
Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?
Click to expand...
Click to collapse
My ROMs have never been on the root of my SD card (I like to organize all my ZIPs in folders)... Probably not a good idea haha. And I have always wiped boot last... never been bricked. I've been boot looped but that's always been a bad ZIP file's fault. And I make NANDROIDs for just such loops.
Sent from my Nexus S using Tapatalk 2
madd0g said:
Wiping storage ain't like wiping your ass, 1 wipe suffices.
Click to expand...
Click to collapse
Sent from my Nexus S using xda app-developers app
Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same thing for me.
And CWM wipes works perfectly. Don't be so lazy men.
Just do it this way.
One clicks and wipe zips will fail so you should learn what they are doing in case you need to do it yourself.
http://forum.xda-developers.com/showpost.php?p=27350690&postcount=4976
I got this while replying to a text message...
I've been getting quite alot of these, from even various applications. It's driving me nuts!!!!
Is there any (permanent) solution for this??
ROM: Gummy
Kernel version: 3.1.10_IcyGlitch_V14-BS_I896-I897 [email protected] #1
Baseband version: T959TLJL3
I'd be forever grateful if this problem could be solved... I really love this ROM
First I would reboot to recovery, then wipe cache, in advanced wipe dalvik cache, then fix permissions. If the problem comes back , I would back up your apps, msgs, that you want, then, wipe system,cache, wipe data/factory reset, and reflash. Maybe a newer rom.
Sent from my SGH-I897 using Tapatalk 2
This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium
simple man said:
First I would reboot to recovery, then wipe cache, in advanced wipe dalvik cache, then fix permissions. If the problem comes back , I would back up your apps, msgs, that you want, then, wipe system,cache, wipe data/factory reset, and reflash. Maybe a newer rom.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I did the first thing you reommended, it didn't work and to make matters worse, ma phone doesn't pass the boot screen....
I quickly rebooted in recovery and made a nandroid backup - followed your second suggestion but i never made a backup of ma msgs because you didn't say so in the 1st suggestion... i can load new roms but can restore from ma nandroid backup
When you wipe dalvik cache, your phone can and will take several minutes to reboot, because it's rebuilding the dalvik cache. Secondly, wiping dalvik cache and fixing permissions wouldn't cause your phone to not boot. Between my wife's and my phone, I've flashed Roms, updated, experimented, fixed, stuff, etc... hundreds of times, and never has a dalvik cache wipe / fix permissions caused the phone to not boot. Hesitant to try to help, because you seem to be blaming me..... But if you can't restore a nandroid, it could be you're on a kernel in which the nandroid backup/restore feature doesn't work, you are running an earlier ICS build.
Sent from my SGH-I897 using Tapatalk 2.
aduka said:
This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Please elaborate... btw i have a friend tht has the same ROM and doesn't face the same issues like me :/
aduka said:
This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
simple man said:
When you wipe dalvik cache, your phone can and will take several minutes to reboot, because it's rebuilding the dalvik cache. Secondly, wiping dalvik cache and fixing permissions wouldn't cause your phone to not boot. Between my wife's and my phone, I've flashed Roms, updated, experimented, fixed, stuff, etc... hundreds of times, and never has a dalvik cache wipe / fix permissions caused the phone to not boot. Hesitant to try to help, because you seem to be blaming me.
Sent from my SGH-I897 using Tapatalk 2.
Click to expand...
Click to collapse
I'm sorry if i came across like that...
just that the phone is driving me nuts
ALSO.... it's the second time i am seeing where reboot take way longer than usual after restoring from a nandroid backup. I av done quite a few and reboot takes less than 10mins. I attempted one the other day and 2hrs 30mins later all i saw was the splash screen and boot animation, phone HOTT!!
This evening again, it looked as if it was going to do the same thing thing... it passed 20mins, i can't sit around waiting for that again
It sounds like a flash to stock KK4 (Full Reparation) would be your best bet. If you're already on G. B. bootloaders, I would recommend the NO BOOTLOADER version, no use flashing bootloader unnecessarily. After that, I would flash the rom of your choice, following the instructions in the O. P. line by line.
Maybe a lot more current rom.
http://forum.xda-developers.com/showthread.php?t=1300843
Sent from my SGH-I897 using Tapatalk 2
duwii said:
Please elaborate... btw i have a friend tht has the same ROM and doesn't face the same issues like me :/
Click to expand...
Click to collapse
Then I recommend re-flash the stock kk4 NO BOOTLOADER, format the internal sd, install the ROM again and install all the programs manually, not with the nandroid backup.
Sent from my SGH-I897 using xda premium
No matter what custom rom I try to load on my G2X, it will go through, install the rom, and then when it reboots past the LG screen, it gets to whatever custom boot screen in on the rom, and just locks up. The only way I can get it to boot after that point is to NVFlash back to stock.
Tried searching through this site and google, but can't find a solution.
You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium
mt3g said:
You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.
It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).
cyansky_1 said:
It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).
Click to expand...
Click to collapse
It is a T-mobile G2X, LG-P999DW.
The CM7 link was straight from the CM7 site, it wasn't an experimental mod or anything, it was the stable one listed under the G2X.
http://www.cyanogenmod.com/devices/t-mobile-g2x
ParanoidAndroid via this thread on here: http://forum.xda-developers.com/showthread.php?t=1762647
Domination via this thread: http://forum.xda-developers.com/showthread.php?t=1570017&highlight=domination
Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium
mt3g said:
Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The last time I pulled it directly on my phone, the other times I downloaded via my PC and then copied the file. Had been via external so I tried internal that last time too. I'm close to madness, but I'm also too stubborn to give up.
I was thinking maybe I need to replace the kernel, but I'm not sure whether that's the problem or which Kernel to try if I did need to.
I had a similar issue on a tablet of mine. What version of CWM are you using? Are you using the touch version? The touch version has had some boot problems. Did you try partition the SDCard in the advanced settings? I forget which I used on my phone. Has anyone else partitioned theirs?
Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...
Sooper1138 said:
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.
Click to expand...
Click to collapse
don't root and then try. mostly roms come with super user access so try without rooting it manually.
Sent from my LG-P999
cyansky_1 said:
Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...
Click to expand...
Click to collapse
Using this method in exactly this order worked perfectly. Thank you very much.
Sooper1138 said:
Using this method in exactly this order worked perfectly. Thank you very much.
Click to expand...
Click to collapse
Did you notice what he didn't do.
Sent from my LG-P999
Okay so i ran synergy rom for a bit, loved it and worked good.
I tried flashing CS SG3 ROM
I couldn't get it to boot all the way up, i tried everything odin back to stock and retried, wiping system , everything.
still couldn't get it to boot all the way up so i gave up and ended up going to GALAXY MOD It worked perfectly and i loved it.
But today I tried flashing release 15, it also will not boot up. But when going and flashing release 14.1 again it works perfectly.. does anyone know what my issue is or how to fix it? I'm so confused... do they have something similar that could possibly be the issue?
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
GoonAssJuan said:
Galaxy mof has problems booting on its newest release if you want to flash rls15 be sure to use cwm touch recovery and pick developer's choice not custom
If you do choose custom be sure to put force gpu rendering.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay. I will be trying this. thank you.
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
barrackOBAMA said:
The only thing I can think of is not wipeing?
You can always try a dirtyy flash between ROMs. But if it doesn't fully boot.
Try wiping cache and dalvik cache.
You can also fix permission just to be safe.
Also. Maybe make sure you are on latest CWM? or TWRP.
sent from that young galaxy on clean ROM!
Click to expand...
Click to collapse
I've tried this. lol