I've tried to downgrade my Galaxy S in order to take some backup from the nandroid that I kept (msgs,call log etc) to sms backup and then to upgrade again to 4.4.
I first flashed through .zip 3.3.0.s semaphore kernel (my last 10.2 snapshot was patched) in order to flash snapshotM1 = jb gapps.The kernel was flashed with no problem but when i tried to flash the rom it got aborted (red triangle).
What further must I do to downgrade to 10.2?
Thanks in advance.
Have you tested a recover to an older backup via CWM-Recovery???
ioannis_m said:
I've tried to downgrade my Galaxy S in order to take some backup from the nandroid that I kept (msgs,call log etc) to sms backup and then to upgrade again to 4.4.
I first flashed through .zip 3.3.0.s semaphore kernel (my last 10.2 snapshot was patched) in order to flash snapshotM1 = jb gapps.The kernel was flashed with no problem but when i tried to flash the rom it got aborted (red triangle).
What further must I do to downgrade to 10.2?
Thanks in advance.
Click to expand...
Click to collapse
freakymod2120 said:
Have you tested a recover to an older backup via CWM-Recovery???
Click to expand...
Click to collapse
You mean just flash (after factory reset /wipes etc) the nandroid without the rom that it has been saved in it?(snapshotM1 10.2)
Yeah. You said you have a jellybean nandroid. Why can't you just restore it??
If you first make a nandroid of your kitkat, you can easily go back to jb, make the backups you need, then flash your KK nandroid back, then restore your JB backups.
Sent from my GT-I9000 using Tapatalk
knuckles1978 said:
Yeah. You said you have a jellybean nandroid. Why can't you just restore it??
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I've read from other users that in order to restore an 4.3 (10.2 in our case) nandroid i first have to put a 4.3 kernel on the phone (after factory reset/wipes etc) .When i do that the kernel goes like a butter into the system and when i try to flash the nandroid i'm getting an aborted sign with the red triangle .(my phone says to me no nono no no )
So if i want to go back i simply load the nandroid without the kernel?
ioannis_m said:
I've read from other users that in order to restore an 4.3 (10.2 in our case) nandroid i first have to put a 4.3 kernel on the phone (after factory reset/wipes etc) .When i do that the kernel goes like a butter into the system and when i try to flash the nandroid i'm getting an aborted sign with the red triangle .(my phone says to me no nono no no )
So if i want to go back i simply load the nandroid without the kernel?
Click to expand...
Click to collapse
I had the same issue and eventually had to flash stock ROM before getting back to 10.2 as there was no way I could downgrade from CM11.
wizzdiz said:
I had the same issue and eventually had to flash stock ROM before getting back to 10.2 as there was no way I could downgrade from CM11.
Click to expand...
Click to collapse
I just flashed the previous nandroid (10.2) with total success and no errors.Just flashed it from kit kat to Jellybean without any kind of kernel flashing.
I guess it was wrong to flash previous kernel after all.
ioannis_m said:
I just flashed the previous nandroid (10.2) with total success and no errors.Just flashed it from kit kat to Jellybean without any kind of kernel flashing.
I guess it was wrong to flash previous kernel after all.
Click to expand...
Click to collapse
Glad to hear it... dunno why it din't work for me though.
Pawitp wrote here http://forum.xda-developers.com/showthread.php?t=2526478 under know issues the follow method to get back to CM 10.2:
Flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing) ==> so this should work ...have you tested that?
wizzdiz said:
Glad to hear it... dunno why it din't work for me though.
Click to expand...
Click to collapse
semaphore kernel.rar
I first flashed through .zip 3.3.0.s semaphore kernel (my last 10.2 snapshot was patched) in order to flash snapshotM1 = jb gapps.The kernel was flashed with no problem but when i tried to flash the rom it got aborted (red triangle
You must flash 3.3.0.s semaphore kernel.rar trhough Odin. Then you can flash android 4.3 as usual.
freakymod2120 said:
Pawitp wrote here http://forum.xda-developers.com/showthread.php?t=2526478 under know issues the follow method to get back to CM 10.2:
Flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing) ==> so this should work ...have you tested that?
Click to expand...
Click to collapse
Must have missed that part. Just tried last night again and it worked. Thanks for the info!
No prob nice to hear ,that it works now !!!:good:
wizzdiz said:
Must have missed that part. Just tried last night again and it worked. Thanks for the info!
Click to expand...
Click to collapse
I am also considering downgrading from CM11 to CM10.2 as I have heard CM10.2 gives a better overall performance and stability.
To avoid problems I'll flash the Samsung stock ROM first.
Can anyone else confirm that CM10.2 is working better than CM11?
Related
I can't get my phone to boot into the ROM, it only boots into CWM every time. Even if I restore my Nandroid backup I have it still won't boot into anything but CWM. .
Any ideas?
_Logie said:
I can't get my phone to boot into the ROM, it only boots into CWM every time. Even if I restore my Nandroid backup I have it still won't boot into anything but CWM. .
Any ideas?
Click to expand...
Click to collapse
what rom are you trying to flash?
I was on MIUI Mintberry but then I tried flashing DMORE3.3 and it just messed up. Was not paying attention to what I was doing, stupidly enough.
But I wouldn't mind just getting back into my MIUI MB ROM and then I'll actually flash DMORE properly this time.
_Logie said:
I was on MIUI Mintberry but then I tried flashing DMORE3.3 and it just messed up. Was not paying attention to what I was doing, stupidly enough.
But I wouldn't mind just getting back into my MIUI MB ROM and then I'll actually flash DMORE properly this time.
Click to expand...
Click to collapse
Well i would do a clean install from gingerbread...here is a kit containing ez odin, ezbase GB, and an instruction txt if you want it...and always good to keep handy!
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip
Legend mate. Really appreciate it .
_Logie said:
Legend mate. Really appreciate it .
Click to expand...
Click to collapse
No probs, any problems or unsure of anything just let me know
All working good. Thanks again!
Btw what ROM is that? It's pretty nice.
_Logie said:
All working good. Thanks again!
Btw what ROM is that? It's pretty nice.
Click to expand...
Click to collapse
It was made by Nitr8, just a stripped down GB based on his insanity ROM
Very nice ROM! So, there's no chance I could now just restore to my MIUI Nandroid backup?
_Logie said:
Very nice ROM! So, there's no chance I could now just restore to my MIUI Nandroid backup?
Click to expand...
Click to collapse
I really couldn't tell you, not familiar with miui, but you can always try,
I have the same issue here. I was running CM9 nightly and everything was working great for weeks. Then my android core process crashed and I decided to reboot the phone, but it got stuck and kept boot looping, i.e. not even making it to the CM9 boot animation and not allowing me to get a logcat.
I used ODIN to flash FixRecovery.tar.md5 and that allowed me to get into CWM recovery. I then cleared Dalvik cache, re-flashed CM9, rebooted but the phone always boots into CWM and never gets to the ROM. I even tried flashing Semaphore kernel in ODIN and re-flashed CM9 several times but to no avail.
My phone just keeps booting into CWM! Is there something I can do to fix this without having to restore to Gingerbread and lose all of my settings and data?
You can go back to the Original Firmware: https://www.fixmystuff.in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom.46/
Then you may root: https://www.fixmystuff.in/FMS_Forum...-i9000-rooting-gt-i9000-2-3-3-india-ddjv9.47/
I had same problem with a galaxy s plus. I've installed the teamwin recovery and with that i flashed the broodrom. After that i got in a bootloop/recoveryloop.. The fix for that was just flashing the bootloader with odin So there was no need to reflash whole rom
aaronegger said:
I had same problem with a galaxy s plus. I've installed the teamwin recovery and with that i flashed the broodrom. After that i got in a bootloop/recoveryloop.. The fix for that was just flashing the bootloader with odin So there was no need to reflash whole rom
Click to expand...
Click to collapse
how do i find a bootloader? i think my phone is in a recovery loop, only starts in CWM
can you please provide me with a new link, i have a GT-i9000 keeps rebooting after i tried flashing with Odin . and can't access to recovery .
thank you for the help.
slaphead20 said:
Well i would do a clean install from gingerbread...here is a kit containing ez odin, ezbase GB, and an instruction txt if you want it...and always good to keep handy!
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip
Click to expand...
Click to collapse
Download URL that works
This link worked for me:
dropbox (dot) com/s/uskxoogzkx3lk8y/dbdata.zip
Sorry can't post urls properly, I'm a new user
I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??
blackinches said:
I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??
Click to expand...
Click to collapse
Your mistake
1) Using Rom manager
2)Devil kernel uses both cwm and twrp recovery no need to "flash recovery" anyways.
If you can still get in to recover just flash what ever ICS rom you want. I'd advice full wipe and formating /system.
Sent from my SGH-I897 using Tapatalk 2
Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?
Pad10 said:
Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?
Click to expand...
Click to collapse
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.
m1batt1 said:
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.
Click to expand...
Click to collapse
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?
Pad10 said:
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?
Click to expand...
Click to collapse
the google apps package you have... is it the one for JellyBean?
m1batt1 said:
the google apps package you have... is it the one for JellyBean?
Click to expand...
Click to collapse
It's called "gaps-jb-20120726". The link is in the description of the cm10 thread.
Any help?
Help
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.
PantherZA said:
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.
Click to expand...
Click to collapse
Okay and how can I do that?
:laugh:
Any help?
Pad10 said:
Okay and how can I do that?
:laugh:
Click to expand...
Click to collapse
By utilizing the sticky threads that have all the information you need.
Pad10 said:
Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=746
My phone running panadroid rom, after wipe data cache and install 4.1.1 rom leak my phone got bootloop. I mean stop at GT 7000 screen or samsung logo or enter the language choice screen then automatic reboot....
Can anybody upload the nandroid backup of 4.1.1 leak. I need it to restore my phone i think that's only way to my phone come up to 4.1.1
Did you tried to reflash the rom?
Or just flash a Safe Kernel like Hydracore first, then full wipes and flash stock ics rom via Odin.
Then reflash Safe Kernel and retry to flash 4.1.1 ROM.
joosh3 said:
Did you tried to reflash the rom?
Or just flash a Safe Kernel like Hydracore first, then full wipes and flash stock ics rom via Odin.
Then reflash Safe Kernel and retry to flash 4.1.1 ROM.
Click to expand...
Click to collapse
Yes i was. But also stop at language choosing screen .
Oh, try to flash another ROM based on XXLS2 Leaked or some custom ROM
Load the *.zip of the ROM on your SD Card and do format /system and all wipes (remember to use safe kernel)
Then flash and i hope it work :crying:
joosh3 said:
Oh, try to flash another ROM based on XXLS2 Leaked or some custom ROM
Load the *.zip of the ROM on your SD Card and do format /system and all wipes (remember to use safe kernel)
Then flash and i hope it work :crying:
Click to expand...
Click to collapse
I haved try alot of custom rom and also stay at language choosing then reboot. I must using nandroid backup to restore to panadroid rom. I thing my devide have problem with flashchip and i need nandroid backup file of 4.1.1 to update to leakrom
Can any body upload your nandroid backup file of 4.1.1 (( Many thankssssssss
That's bad, you never did some Nandroid backup of previous ROM's you used?
If yes try to restore it.
If not im sorry, i don't have what you need :crying:
joosh3 said:
That's bad, you never did some Nandroid backup of previous ROM's you used?
If yes try to restore it.
If not im sorry, i don't have what you need :crying:
Click to expand...
Click to collapse
Yes i have backup of panadroid and restore successfully. But now i can't install JB TW rom anymore
godoflove1988 said:
Yes i have backup of panadroid and restore successfully. But now i can't install JB TW rom anymore
Click to expand...
Click to collapse
The best thing is that your device isn't bricked. Did you tried as i said before? flashing Stock ICS ROM via Odin (not only custom Roms) , then Safe Kernel and start to flash JB ROM from this?
joosh3 said:
The best thing is that your device isn't bricked. Did you tried as i said before? flashing Stock ICS ROM via Odin (not only custom Roms) , then Safe Kernel and start to flash JB ROM from this?
Click to expand...
Click to collapse
Yes i was flash N7000DXLR2_N7000OLBLR1_N7000DXLR1_HOME.tar. And Phil kernel and then stuck at language choosing menu => reboot automatically
godoflove1988 said:
Yes i was flash N7000DXLR2_N7000OLBLR1_N7000DXLR1_HOME.tar. And Phil kernel and then stuck at language choosing menu => reboot automatically
Click to expand...
Click to collapse
Try to flash this one: N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar.md5
You can download it from here: N7000XXLRQ_N7000DBTLRQ_DBT.zip
After download extract it and flash via Odin.
Hope it work (remember safe kernel)
godoflove1988 said:
Yes i was flash N7000DXLR2_N7000OLBLR1_N7000DXLR1_HOME.tar. And Phil kernel and then stuck at language choosing menu => reboot automatically
Click to expand...
Click to collapse
Just boot into Philz recovery and do factory reset. Phone should boot properly after that
Sent from my GT-N7000 using xda app-developers app
Well, it so happened that I was on omni rom 4 3.1 with cocore kernel twrp recovery and I saw in a thread that we can theme our recovery by adding a ui.zip file in the theme folder of twrp. Ever since then, my phone boots in recovery only (without the three button combination). Plus in twrp, the theme is applied but I get a super zoomed view of the recovery so I can't restore nandroid as well. Of course, I used my last resort and brought back my phone to stock through odin but the problem is what did I do wrong and what should I take care of to prevent this sort of **** from happening in the future?
Sent from my GT-I9070 using xda app-developers app
Why did you use the co-core kernel for a cm ROM??
The rom shouldn't boot if you did this..
BTW You are getting the super zoomed recovery maybe because you are using the ui.zip designed for a mdpi/ldpi screen resolution.
Our screen is hdpi.
Sent from my GT-I9070 using Tapatalk
But I used the ui.zip for hdpi devices only.. and I dont know.. the rom just flashed when I used cocore. By the way.. I dont see any other method for obtaning recovery except shaan's temporary cwm.. is there any other method as well??
Sent from my GT-I9070 using xda app-developers app
RazaVakil7995 said:
Well, it so happened that I was on omni rom 4 3.1 with cocore kernel twrp recovery and I saw in a thread that we can theme our recovery by adding a ui.zip file in the theme folder of twrp. Ever since then, my phone boots in recovery only (without the three button combination). Plus in twrp, the theme is applied but I get a super zoomed view of the recovery so I can't restore nandroid as well. Of course, I used my last resort and brought back my phone to stock through odin but the problem is what did I do wrong and what should I take care of to prevent this sort of **** from happening in the future?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Do not mess with something that you are not sure that works on our phone. If you read that someone that has I9070 phone is using something, you can use it. Searching and using stuff from other phones can make you mess like that you got.
Omni MUST use its kernel, you CAN'T use COCORE on it. You will end up with a bootloop if you use COCORE on OMNI.
What you need to do is to flash stock FIRMWARE with ODIN. Download CoCore kernel, UNPACK it and use KERNEL.BIN.MD5 (copy to phone memory). Install UKF and ROOT EXPLORER. Open Universal kernel flasher and follow the procedure to install COCORE. Install, reboot and you have permanent recovery (CWM or TWRP depends what CoCore version you choose).
Perhaps you guys misunderstood me.. I did not flash cocore on Omni.. I flashed cocore on stock and then I flashed omni rom.. so I guess I have permanent recovery..
Im sorry if I sound like a noob but hey, every expert was once a noob, Im learning
I agree to the part of messing with things that people Dont use on our phone, I'll see to that in future..
Sent from my GT-I9070 using xda app-developers app
RazaVakil7995 said:
Perhaps you guys misunderstood me.. I did not flash cocore on Omni.. I flashed cocore on stock and then I flashed omni rom.. so I guess I have permanent recovery..
Im sorry if I sound like a noob but hey, every expert was once a noob, Im learning
I agree to the part of messing with things that people Dont use on our phone, I'll see to that in future..
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I missunderstood. Because you wrote: "that I was on omni rom 4 3.1 with cocore kernel twrp"
P.S. Maybe that theme problem have something to do with version of TWRP. But I can't tell for sure.
dagger said:
Why did you use the co-core kernel for a cm ROM??
The rom shouldn't boot if you did this..
BTW You are getting the super zoomed recovery maybe because you are using the ui.zip designed for a mdpi/ldpi screen resolution.
Our screen is hdpi.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
By the way, why did you tell the rom should not boot? Is it because the cocorekernel is only supported on android 4.1 or some other reason?
shut_down said:
I missunderstood. Because you wrote: "that I was on omni rom 4 3.1 with cocore kernel twrp"
P.S. Maybe that theme problem have something to do with version of TWRP. But I can't tell for sure.
Click to expand...
Click to collapse
And when I went from omni rom to cm11 by maclaw, my recovery changed to cwm... any idea why did this happen because I was supposed to have permanent twrp
RazaVakil7995 said:
And when I went from omni rom to cm11 by maclaw, my recovery changed to cwm... any idea why did this happen because I was supposed to have permanent twrp
Click to expand...
Click to collapse
The recovery in our phone is dependent on the kernel.
So if the kennel changes, the recovery changes..
Sent from my GT-I9070 using Tapatalk
custom recovery in cm11
So if i flash from stock rom jb to cm11 (tc) , the recovery changes to cwm , no matter if u had CoCore+cwm or CoCore+ TWRP in stock rom.
What happens to the kernel in cm11?
i have done nandroid backup with TWRP, but since recovery changes to cwm in cm11 , will i no longer be able to restore the backup ?
Would it be better to do a nandroid backup with CoCore+Cwm then?
[email protected] said:
So if i flash from stock rom jb to cm11 (tc) , the recovery changes to cwm , no matter if u had CoCore+cwm or CoCore+ TWRP in stock rom.
What happens to the kernel in cm11?
i have done nandroid backup with TWRP, but since recovery changes to cwm in cm11 , will i no longer be able to restore the backup ?
Would it be better to do a nandroid backup with CoCore+Cwm then?
Click to expand...
Click to collapse
If you flash stock JB firmware you get stock recovery (not CWM or TWRP). And you can't use nandroid backup of JB if you are on CM11 because Preload partition is used for SWAP, and it will be non usable for JB. You must flash script to repartition it or flash stock JB firmware. If you have TWRP backup, flash stock JB, root it, install CoCore with TWRP recovery and there you go...
Backup
shut_down said:
If you flash stock JB firmware you get stock recovery (not CWM or TWRP). And you can't use nandroid backup of JB if you are on CM11 because Preload partition is used for SWAP, and it will be non usable for JB. You must flash script to repartition it or flash stock JB firmware. If you have TWRP backup, flash stock JB, root it, install CoCore with TWRP recovery and there you go...
Click to expand...
Click to collapse
Thank you. So i understand that nandroid backup is useful only when something goes wrong during the process of upgrading from stock JB to CM11 .
one more doubt, I have also backed up app user data + system data with Titanium Backup Pro. That can be used to restore all data after i upgrade to cm11 right? Will Titanium Backup Pro take care of efs ( related to IMEI no.) if something goes wrong after flashing cm11. Btw i have also backed up efs with Samsung Tools app.
Also could you enlighten me about my first question in previous post " what happens to kernel in cm11" ?
[email protected] said:
Thank you. So i understand that nandroid backup is useful only when something goes wrong during the process of upgrading from stock JB to CM11 .
one more doubt, I have also backed up app user data + system data with Titanium Backup Pro. That can be used to restore all data after i upgrade to cm11 right? Will Titanium Backup Pro take care of efs ( related to IMEI no.) if something goes wrong after flashing cm11. Btw i have also backed up efs with Samsung Tools app.
Also could you enlighten me about my first question in previous post " what happens to kernel in cm11" ?
Click to expand...
Click to collapse
CM11 ROM 4.4.2 or 4.4.3 is the result of an update of version 4.1.2 of Android Jelly Bean. If right now, you have a backup system and applications that have been stored in the system when you are Jelly Bean. Then you want to restore the backup to the CM11, then I guess you will get an error. Because the system is Jelly Bean, and Kitkat system is 2 different things in the context of the "system". So you can do this while using TB Pro applications only restore data only, such as: backup contacts, sms / mms, third-party applications such as, apk, application of playstore etc.. Not the whole system ROM previously, JB.
Related to the kernel, system jelly bean, and kitkat system, has different kernel. In this case the kernel is owned by CM11 ROM, not the stock ROM 4.4.2/4.4.3 by samsung. CM11 kernel 4.4.2/4.4.3 allows us to perform GPU OC and CPU OC/UC/OV/UV In the default kernel Stock ROM (JB), you will not be able to do it, unless you replace it with a custom kernel, as the Cocore kernel. Hopefully it can be more clear.
Phone got stuck in a bootloop after flashing 4.4.2 Pac Man, the latest release. Also I can't get to recovery mode using Volume Up + Volume Down + Power. Help
Mergk said:
Phone got stuck in a bootloop after flashing 4.4.2 Pac Man, the latest release. Also I can't get to recovery mode using Volume Up + Volume Down + Power. Help
Click to expand...
Click to collapse
We need more info. What was on the phone before you flashed Pac Man? Also, did you flash anything else with it?
BWolf56 said:
We need more info. What was on the phone before you flashed Pac Man? Also, did you flash anything else with it?
Click to expand...
Click to collapse
That's all. I just updated the rom. I followed the steps given in updating the rom. No, only the rom.
I think there's no problem in how I flashed the rom. Maybe the rom itself is the problem because after flashing back to stock Gingerbread, I rooted my phone, flashed a kernel with cwm, installed root, did full wipe and flashed the rom but still stuck on bootloop. Thanks for trying to help.
Mergk said:
I think there's no problem in how I flashed the rom. Maybe the rom itself is the problem because after flashing back to stock Gingerbread, I rooted my phone, flashed a kernel with cwm, installed root, did full wipe and flashed the rom but still stuck on bootloop. Thanks for trying to help.
Click to expand...
Click to collapse
Coming from GB, you have to repartition, which means that you have to flash the ROM twice in order for it to boot.
BWolf56 said:
Coming from GB, you have to repartition, which means that you have to flash the ROM twice in order for it to boot.
Click to expand...
Click to collapse
How do I repartition?
I'm still on gingerbread with corn kernel, how should I flash the rom?
Mergk said:
How do I repartition?
I'm still on gingerbread with corn kernel, how should I flash the rom?
Click to expand...
Click to collapse
Like I said, flash it twice in a row. Also don't forget the GApps if it's a AOSP ROM.