I have a p7510 that is Canadian, but I have flashed an American 3.2 rom which I've rooted with CWM 5.5.04. I've been trying to load up Maple Syrup's Jellybean July 18 build. I first flashed this dirty. But I got the flashing X screen for like 15 minutes. Then I tried a different download of CWM 5.5.0.4 because my system was coming up on the computer as a p7500. I thought perhaps I had the wrong cwm. So I went back to 3.2 to do a clean wipe. I've done this twice, reflashing JB after I would root 3.2 again. I have had no luck getting JB to get beyond the flashing animation. Any advice?
Fix
HunchedoverPhone said:
I have a p7510 that is Canadian, but I have flashed an American 3.2 rom which I've rooted with CWM 5.5.04. I've been trying to load up Maple Syrup's Jellybean July 18 build. I first flashed this dirty. But I got the flashing X screen for like 15 minutes. Then I tried a different download of CWM 5.5.0.4 because my system was coming up on the computer as a p7500. I thought perhaps I had the wrong cwm. So I went back to 3.2 to do a clean wipe. I've done this twice, reflashing JB after I would root 3.2 again. I have had no luck getting JB to get beyond the flashing animation. Any advice?
Click to expand...
Click to collapse
OK, now I'm giving my self some advice, or sharing my wisdom. After about 5 or 6 attempts to flash JB with CWM 5.5.0.4, I finally decided to try 5.8....through rom manager. I should have known that this might work, because I had been having trouble backing up my files with 5.5, but it worked quite well with 5.8. Anyway, JB is running smoothly now. I found that Rom Manager with CWM 5.8 and a clean install did the trick.
Thanks again for the rom all you hard workers out there.
Related
Hi, been lurking, great forum, seems like lots of help here.
History of what I have done
I am new to rooting and flashing roms. I followed a step by step guide on how to root my gt-i9100m and install custom rom. The custom rom was Rainbox v7. poor battery life, followed another guide and installed siya kernel which was not compatible. reloaded philz kernel, everything was fine. Tried to update to rainbox 8.3, got stuck in boot loop, did full backup and wipe prior. attempted a restore, still stuck in boot loop. recovery menu was siya recovery. enter recovery again after restore, now in philz? performed another recovery using philz recovery, still stuck in boot image loop with black screen in between. from philz recovery i re flashed rainbox v7 zip, and i seem to have fixed it.
What went wrong? How do I avoid doing this again, is there an updated rainbox that i can install?
Please help, also, I am not fully versed with the short terms you often use, please be patient.
When moving around JB aka Jelly Bean or from an ICS aka Ice cream sandwich -=or=- GB aka Ginger Bread to JB... flash that particular roms kernel (or compatible) before trying new rom or restoring nandroid aka... you get the picture
Sending...
So I've been on CM9 since October, everything has been all well and good! Today I decided I wanted to flash a unbranded GS2 ICS ROM onto my phone so I could then update via KIES to the new JellyBean one. But now my phone will not go past the boot logo since I flashed I9100XWLPT via ODIN in the PDA section just as the guide told me. The boot logo moves but will not go past it. I have flashed a new kernel, I then tried Syiah Kernel. Now I've reflashed Cyanogen mod 9 via CWM and it is doing the same thing. The boot animation just moves forever. Can anyone help?
yes flash jb straight up.
Sent from the little guy
Wipe data/cache and dalvik-cache then re-flash a JB ROM (since you want to use Jelly bean) via Odin. You can get JB Roms from here
I've wiped all caches then flashed the JB SII ROM and still the same problem, it boots up to the samsung logo then just replays it over and over again without getting into the phone
And factory reset does nothing?
Flash this. See how you do.
PS: Flash only CODE, PHONE and CSC.
Ok, because I was so happy with cyanogenmod on my galaxy s I decided to try to install it on my SII.
Silly me, I decided to follow the instructions. couldn't get my trusty odin working, even after a couple of reboots and reinstalls of kies. Heimdall turned out to be the 64 bit version so I needed to find the 32 bit version. Long story short, the instructions sucked...
Then, I tried to install the suggested cwm. After a reboot, my phone entered a bootloop. I could enter recovery but trying to flash cm10 gave me "Status 7 blabla".
So, I searched on the web for a stock rom to at least get my s2 working again, found one and flashed it. Market keeps on crashing and it's version 4.0.3.
I tried reflashing cwm, cf-root and time and time again it kept creating a bootloop after which I had to reflash the rom with the broken market to get everything working again.
My questions are:
where did I go wrong in flashing cwm? Is there a different version I should flash? what's up with the extremely bad cyanogenmod instructions? Can someone get the market working again?
can someone guide me step by step through the process?
Why don't you flash it via recovery?
Sent from the little guy
gastonw said:
Why don't you flash it via recovery?
Sent from the little guy
Click to expand...
Click to collapse
because it gives the error "status 7"
I can't install a cwm that doesn't bootloop (I can however enter recovery) and in recovery I can't flash a thing because it throws errors at me
Assuming that you are on stock samsung ICS ROM, flash Siyah kernel from Odin
http://d-h.st/Bcf
After this you will get CWM recovery from which you can flash any i9100 CM version.
Sent from my GT-N7100 using Tapatalk 2
quick follow-up:
I had another laptop laying around that was never poisoned by samsung kies, so I decided to give it a try. installed the usb-drivers and used odin to flash another stock-rom version (that actually worked this time )
Then, I flashed cf-root and upgraded to cyanogenmod without any problem.
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
Hi fellas,
so here is my issue. I got a unbranded SG2 with the latest stock JB firmware on it. I rooted with frama root, flashed the SiyahKernel S2-v6.0beta5 with Odin. Everything worked fine to this point. :victory: Then I mounted cyanogenmod 10.2 (cm-10.2-20131226-NIGHTLY-i9100.zip) as a 2nd ROM via CWM Recovery. I followed the various instructions you can find. After rebooting I got stuck in a bootloop. I tried various fixes but I´m still bootlooping. CWM Recovery and DL Mode are still accessible. I guess I got bricked. How do I fix this?
Btw.: Unfortunately was too retarded to do any backups. Shame on me. :silly:
Thanks 4 your help in advance and sorry 4 wasting your time...
28k-Lag said:
Hi fellas,
so here is my issue. I got a unbranded SG2 with the latest stock JB firmware on it. I rooted with frama root, flashed the SiyahKernel S2-v6.0beta5 with Odin. Everything worked fine to this point. :victory: Then I mounted cyanogenmod 10.2 (cm-10.2-20131226-NIGHTLY-i9100.zip) as a 2nd ROM via CWM Recovery. I followed the various instructions you can find. After rebooting I got stuck in a bootloop. I tried various fixes but I´m still bootlooping. CWM Recovery and DL Mode are still accessible. I guess I got bricked. How do I fix this?
Btw.: Unfortunately was too retarded to do any backups. Shame on me. :silly:
Thanks 4 your help in advance and sorry 4 wasting your time...
Click to expand...
Click to collapse
Siyah dont support dualboot anymore... flash stock rom via download mode..and try to do it with dorimanx kernel instead.
In addition to this the Siyah does not support the ROM 4.3 !