I have a question.. I wanted to try out the Apex rom and I wasn't sure if I need to go all the way back to stock or can I go from Serendipity VII directly to Apex??
Any help is greatly appreciated..
mrhatfi said:
I have a question.. I wanted to try out the Apex rom and I wasn't sure if I need to go all the way back to stock or can I go from Serendipity VII directly to Apex??
Any help is greatly appreciated..
Click to expand...
Click to collapse
You can go directly from Serendipity VII to Apex 10. Serendipity VII have GB Bootloaders, so it will be no problem. Just remember to Wipe Data/Factory Reset, Wipe Cache and Clear Devilk Cache before install Apex 10 Zip from ClockworkMod.
You do not need to wipe anything before flashing a ROM. The ROM installation script should do it for you
Why the switch?
Thanks Guys.. It worked perfectly..
xThe Enforcer said:
Why the switch?
Click to expand...
Click to collapse
I was just in the mood to try something new.. I have loved Serendipity VII.. I haven't flashed anything lately so I wanted to play with something different..
watsa I have a question for you... I tried installing the TalonDev kernel and for some reason I can no longer turn on my Wifi.. I toggle it on and then it doesn't find any wifi spots then it just shuts itself off.. Any ideas how to correct this? I see you use that kernel and I was wondering if you had that issue before..
Any help would be greatly appreciated..
I figured it out.. I was using the 0.4.3 version of the Kernel and that was what was causing the issues.. As soon as i switched to the 0.5.1.2 kernel the problem was gone.. And now everything is as it should be..
Thanks again for your help!
Related
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
jonslaught said:
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
Click to expand...
Click to collapse
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Mr. Apocalypse said:
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Click to expand...
Click to collapse
I've wiped everything multiple times and flashed just the eg rom on its own and it still sends me back to recovery. x.x
i'm using g2x nullifier to see if after doing that, then flashing any rom will make it work.
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
I would a give a shot of this tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize all your partitions.
Sent from my LG-P999 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
ratza66 said:
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
Click to expand...
Click to collapse
was looking around for some tool like this and couldn't find it x.x
I used it and presto! my g2x is alive and kicking again, thanks alot man
And thanks to everyone else that bothered posting, really helps alot
Hello - I tried to update my phone from Infuse v2.2.3 to Th3Bill JB 3.3.2 and got in an endless loop. I then tried to go into recovery mode and do a restore. Checked the MD5, Erased boot and then started restoring boot image and thats where she has been sitting for some time. I will pull batter and attempt again however I may be hosed. Any help greatly appreciated.
It is not possible, that I am aware of, to go from Froyo straight to JB. You will also not be able to restore a backup at this point due to changes made on the phone in the borked attempt. You should be able to wipe data, cache, and dalvik, and after a couple of attempts re- install a Froyo rom from scratch. If you can't do that, do this.
http://forum.xda-developers.com/showthread.php?t=1629079
Thanks to qkster and Entropy for this.
I had that issue as well. Only cause I like to see if I can be done. But no. What I do is go back to stock and rooted then flash a ICS ROM then make sure it boots. Then go wipe all stuff in cwm and flash jelly
Sent from my SGH-I997 using xda app-developers app
Hey Pony, I was on the custom ROM Infuse v2.2.3 and not stock Froyo. I ended up doing the gtg ultimate unbrick to bring it back to stock and then did the full back to Infuse v2.2.3 and then did a nandroid restore. Everything looks good but it is acting a bit weird. Like I will try to open my applications or folders it sometimes hangs. I consistantly get it to free up by locking the phone and then unlocking it. Weird huh? Anyway I would be interested in trying to upgrade to JB but would like more instruction on that. Thanks for responding and if you can recommend anything that might help Im all ears.
See the post below - if you need more specific instructions let me know.
Thanks rkkaranrk.
Use Odin or heimdll to get stock GB Tom and then from there u can flash any rom u like just follow the instructions in the OP. You can go directly from GB to ICS but for JB u have to flash any ICS rom first and then JB.
Read the instructions on every thread.
Sent from my MB855 using Tapatalk 2
"Update Gone Wrong" ,Sounds like a Reality Show.
Truckerglenn said:
"Update Gone Wrong" ,Sounds like a Reality Show.
Click to expand...
Click to collapse
Lmfao! Yes...
The only reality show that follows Android Phone Development, and the dangers and drama of rooting and tweaking phones.
It'll be a hit!
Posted from my Paranoia Infused Android, now featuring Butter flavored JellyBeans!
so I am rooted and have superuser access. trying to get ics on this thing and from what ive read you have to go to gb then to ics. so i downloaded cm7 to get to ginger bread. everything flashed fine but when rebooting from recovery its just hanging at the samsung logo. sorry if i sound like a noob. im really not, i just have a galaxy nexus so i haven't rooted a non nexus phone in a very long time. especially one still running froyo. any info would be a huge help
kendall316 said:
so I am rooted and have superuser access. trying to get ics on this thing and from what ive read you have to go to gb then to ics. so i downloaded cm7 to get to ginger bread. everything flashed fine but when rebooting from recovery its just hanging at the samsung logo. sorry if i sound like a noob. im really not, i just have a galaxy nexus so i haven't rooted a non nexus phone in a very long time. especially one still running froyo. any info would be a huge help
Click to expand...
Click to collapse
Have you tried booting back into recovery and flashing the same rom once more?
Also, did you make sure to wipe all data, cache, dalvik cache and such before flashing the rom?
My suggestion: use heimdall one-click uclb3, and preferably also flash GB bootloaders (to avoid rainbows in ics or jb recovery). Flash Entropy's dd kernel which will give you red cwm, and from there you are ready to flash ICS.
Sent from my sweet & buttery Infuse
Ryo Misaki said:
Have you tried booting back into recovery and flashing the same rom once more?
Also, did you make sure to wipe all data, cache, dalvik cache and such before flashing the rom?
Click to expand...
Click to collapse
yes to both
kendall316 said:
yes to both
Click to expand...
Click to collapse
No luck? =(
Give Andros' suggestion a go. Even with bootloops, you can still put your Infuse in Download Mode to use Hemdall or Odin.
Ryo Misaki said:
No luck? =(
Give Andros' suggestion a go. Even with bootloops, you can still put your Infuse in Download Mode to use Hemdall or Odin.
Click to expand...
Click to collapse
Before you go and bite my head off, listen
first time i was upgrading a rom, i thought i was at a samsung boot logo freeze, and it took my phone around 20 minutes to fully upgrade, if this isnt your problem, then i miss understood, and recently, ive started using odin, and it is much easier than using the cmw
Reading and research is always the answer to everything.
http://forum.xda-developers.com/showthread.php?t=1700416
I'm having the hardest time flashing the ktoons kernel for jellywiz...I downloaded the kerned, wiped cache and dalvik, installed kernel, fixed permissions and then rebooted...When I reboot the screen gets stuck on Samsung Galaxy SIII...I do a battery pull and the same thing happens and I have to restore my backup...Could anyone try and help me please? Step by step would be greatly appreciated! Thanks!
pschatz12 said:
I'm having the hardest time flashing the ktoons kernel for jellywiz...I downloaded the kerned, wiped cache and dalvik, installed kernel, fixed permissions and then rebooted...When I reboot the screen gets stuck on Samsung Galaxy SIII...I do a battery pull and the same thing happens and I have to restore my backup...Could anyone try and help me please? Step by step would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
You did all the right things in terms of flashing process.
The problem is with the kernel. JellyWiz is mostly stable but it still has bugs. Add on top of that a new test kernel. Problems are to be expected.
I wouldn't expect to have stable kernels until we have a fully functional JB ROM first.
Sent from a SYNERGIZED GalaxySIII
The reason you can't flash that kernel on Jellywiz is because neither KT747 kernel is actually made for Jellywiz. I don't know what choices you have besides the default one for now, but that's actually why it won't work. I think ktoonsez said this himself. Or maybe you just loaded the wrong one. Maybe one works
Zalithian said:
The reason you can't flash that kernel on Jellywiz is because neither KT747 kernel is actually made for Jellywiz. I don't know what choices you have besides the default one for now, but that's actually why it won't work. I think ktoonsez said this himself. Or maybe you just loaded the wrong one. Maybe one works
Click to expand...
Click to collapse
I believe there is a test ktoons kernel now that's meant for jellywiz.
Sent from a SYNERGIZED GalaxySIII
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.