Database Info

(Q) jellybam 1.3 won't flash

Hi guys. Al thou this is my first post I've been flashing my i9003 for a year or so and i've never had any problems until now.
I have an stock gingerbread installed (XXKPQ) that I flashed using odin, kernel version (2.6.35.7-CL709629 [email protected] #1)
Just so you know, I'm from Argentina, and in order to be able to use 3g, had to keep the modem in I9003LUBKB1 version.
I also flashed cf root (by Skin1980) and I'm using CWM v1.80
I get the latest jellybam (1.3) from this post: http://forum.xda-developers.com/showthread.php?t=1972087
And followed the instructions in the official website : http://www.igio90.net/how-to-install/
Just in case you're too lazy to follow the link here are the instructions:
What to do if you are coming from a Stock, CyanogenMod, MIUI, AOKP and any other custom ROM different from JellyBam
-Download the latest revision of JellyBam ROM for your device
-Place the zip into your internal SDCard
-Boot into CWM recovery (Home+Power+Volume up until samsung logo appear)
-Wipe data/factory reset
-Wipe dalvik cache (Inside advanced tab)
-Install zip from internal SDCard
-Welcome to JellyBam!
(I had to wipe the data first and then put the zip in the sd card because wiping the data was erasing the jellybam zip)
The first time I run the installer it got stuck at 50% while installing sony's media player. So i just started the process again and uncheked sony walkman player, it installed "successfully".
When the phone restarted, it was just the old gingerbread, in the about phone panel, it was all the same that before installing jellybam.
So it obviously didn't installed. I can make calls, send and receive messages, wifi is working fine.
So can anyone tell me what am I doing wrong? Do i have to flash a jellybean kernel?, I dont really know hoe to do that but I'm sure there's more than one post around here that explains that process.
If this question has already been posted I'm really sorry, I did search for any post that could help me with this problem but I didn't find any real answer.
I really hope somebody can help me, and sorry for the bad english, I did study the language but it was a long time ago.
Thanks everybody, specially to developers, you're awesome.:good:

I think you should fist flash theJellyBam v1.1.0 alpha4 in order to repartition before flash the v1.3. hope it can help u.
Sent from my GT-I9003 using xda app-developers app

friend, 1st thing, you need to flash newer cwm to minimum your problem. now is version 6 on CM10 rom.
2nd flash CM rom or AOSP to use jelly bam
Sent from my Galaxy Nexus using Tapatalk 2

flashing 1.1 first worked great.
I'm having issues thou, don't know if this are known bugs or just happens to me.
I can't get any signal, gonna try flashing this:
http://forum.xda-developers.com/showthread.php?t=2029921&highlight=cm10+signal+fix
And seems like the phone can't detect when it's plugged to a usb port

narshade said:
(I had to wipe the data first and then put the zip in the sd card because wiping the data was erasing the jellybam zip)
Click to expand...
Click to collapse
Wiping the data does not affect your Internal/External storage.

chongns said:
friend, 1st thing, you need to flash newer cwm to minimum your problem. now is version 6 on CM10 rom.
2nd flash CM rom or AOSP to use jelly bam
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First of all thank you for your helpful answer (I clicked the thank you button).
I have cwm version 5 and I have been having the same problem than the OP. I'd like to flash a CM rom before going on to JB 1.3 so my question is, knowing that I currently have an I9003XXKPR 2.3.6 rom, can I flash CM 10 or should I start by a previous version? And, if so, which one?
Thank you for your help.

jawadlotfi said:
First of all thank you for your helpful answer (I clicked the thank you button).
I have cwm version 5 and I have been having the same problem than the OP. I'd like to flash a CM rom before going on to JB 1.3 so my question is, knowing that I currently have an I9003XXKPR 2.3.6 rom, can I flash CM 10 or should I start by a previous version? And, if so, which one?
Thank you for your help.
Click to expand...
Click to collapse
i think you should start from zero. take a backup of your files, flash a stock rom and then use universal cf root to root your phone. then flash cm 10 alpha 4 and then the jellybam 1.3. that's the way i have flashed mine. i hope it helps.

imboy25 said:
i think you should start from zero. take a backup of your files, flash a stock rom and then use universal cf root to root your phone. then flash cm 10 alpha 4 and then the jellybam 1.3. that's the way i have flashed mine. i hope it helps.
Click to expand...
Click to collapse
Thanks for the advice, I flashed a stock rom in the meantime so I am ready to flash CM 10 alpha 4.
Take care

jawadlotfi said:
Thanks for the advice, I flashed a stock rom in the meantime so I am ready to flash CM 10 alpha 4.
Take care
Click to expand...
Click to collapse
Good luck! i hope you flash it correctly! just read and follow the instructions in the cm10 thread thoroughly so you can avoid any problems.

All custom rom unofficial, not compile, but directly modify our base cyanogen
It is recommended to start on a CM10 origin
Example A3 to A4
KPE> LF2> CF-LF2
Wipe Data / Factory Reset. (MUST DO THIS STEP)
Select the CM10 A4.zip from your SD Card and flash.
Auto rebooted into recovery (if it show error mounting / cache, and cant mount in manually mount and storage, do wipe / cache)
Go to Advanced -> Reboot Recovery
Select the CM10 A4.zip from your SD Card and flash again
Go to Advanced -> Reboot Recovery.
Mounts and Storage -> Format dbdata (you would not find this in CWM so just ignor 6)
8. reboot
You can then flash all based on Unofficial Alpha 4
Just do the basic procedure wipe

Help, Stuck at CM boot screen after update to 10.1

I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.

Athanasius said:
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Click to expand...
Click to collapse
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it

mypat said:
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
Click to expand...
Click to collapse
I can't tell you exactly what I did but it seems to be working... somehow a factory reset resulted in CM10.0 and gapps installed correctly... i'm still scratching my head but i'm happy enough.

Unable to install Custom ROM in Tab2 P3110

Hi,
I am unable to Install any custom roms in Samsung galaxy Tab 2( Gt-P3110 ). When ever a custom Rom is placed, It either gets stuck in the Samsung logo, or just shows a 'Blank' Screen and hangs on that screen. After this i have to reflash the stock firmware to get the tab up again... (i do perform the wipe data/cache..then wipe cache. then wipe dalvik cache in this order before flashing the ROM)
The details of the tab are:
Model- GT-P3110 ( Galaxy tab 2 , wifi only )
android version-4.1.2
Build number-JZO54K.P3110DCMA4
Recovery: PhilZ Touch 6 Recovery ( Based on CWM Base version: v6.0.4.5 )
Rooted: Yes
Even the backups made are not complete, restoring a backup restores the tab to factory reset.
(it does say failed to find partition /recovery and /data for a very short time before starting the backup).
I am using a windows 7 system for this.
Thanks for the help...
Regards

akshaydogra said:
Hi,
I am unable to Install any custom roms in Samsung galaxy Tab 2( Gt-P3110 ). When ever a custom Rom is placed, It either gets stuck in the Samsung logo, or just shows a 'Blank' Screen and hangs on that screen. After this i have to reflash the stock firmware to get the tab up again... (i do perform the wipe data/cache..then wipe cache. then wipe dalvik cache in this order before flashing the ROM)
The details of the tab are:
Model- GT-P3110 ( Galaxy tab 2 , wifi only )
android version-4.1.2
Build number-JZO54K.P3110DCMA4
Recovery: PhilZ Touch 6 Recovery ( Based on CWM Base version: v6.0.4.5 )
Rooted: Yes
Even the backups made are not complete, restoring a backup restores the tab to factory reset.
(it does say failed to find partition /recovery and /data for a very short time before starting the backup).
I am using a windows 7 system for this.
Thanks for the help...
Regards
Click to expand...
Click to collapse
change your recovery, find it HERE

150208 said:
change your recovery, find it HERE
Click to expand...
Click to collapse
Hi,
Thanks for the reply.. I am downloading TWRP 2.7.0.0 and will try this out.. Will update the results soon.
UPDATE::
I used the Flashable-ZIP GT-P3110_TWRP_2.7.0.0.zip but now, the tab is again stuck on the samsung logo..
UPDATE2::
Flashed GT-P3110_CWM_6.0.4.7_Swipe-Edition.tar.md5 using ODIN, now tab is booting up.. but only into recovery.

akshaydogra said:
Hi,
Thanks for the reply.. I am downloading TWRP 2.7.0.0 and will try this out.. Will update the results soon.
UPDATE::
I used the Flashable-ZIP GT-P3110_TWRP_2.7.0.0.zip but now, the tab is again stuck on the samsung logo..
UPDATE2::
Flashed GT-P3110_CWM_6.0.4.7_Swipe-Edition.tar.md5 using ODIN, now tab is booting up.. but only into recovery.
Click to expand...
Click to collapse
flash the rom again
make sure you wipe everything before flash to prevent any errors

150208 said:
flash the rom again
make sure you wipe everything before flash to prevent any errors
Click to expand...
Click to collapse
:crying: noluck
I performed the following steps:
1- wiped data/cache
2-wipe cache
2.a- wiped dalvik cache
3-install slim rom with its corresponding gapps ( both installed successfully )
4-reboot system
Now the tab is stuck again on the 'samsung logo' screen.. i gess i will have to flash the stock firmware again for this to work.. :crying:

akshaydogra said:
:crying: noluck
I performed the following steps:
1- wiped data/cache
2-wipe cache
2.a- wiped dalvik cache
3-install slim rom with its corresponding gapps ( both installed successfully )
4-reboot system
Now the tab is stuck again on the 'samsung logo' screen.. i gess i will have to flash the stock firmware again for this to work.. :crying:
Click to expand...
Click to collapse
Iv flashed the stock firmware, and the tab is now non rooted.. Please share the steps that need to be performed, preferably for cyanogen mod ... my odin counter is already @ 25..
:crying::crying::crying:

akshaydogra said:
Iv flashed the stock firmware, and the tab is now non rooted.. Please share the steps that need to be performed, preferably for cyanogen mod ... my odin counter is already @ 25..
:crying::crying::crying:
Click to expand...
Click to collapse
what costum rom did you tried to install?
============
ROOT and update recovery:
HERE is the fastest way to root
reboot to recovery, and flash latest recovery again from HERE
reboot and go to recovery again.
Flashing roms:
Do a back up of important data/rom, place it inside your pc
Inside recovery:
Wipe data
Wipe cache
Wipe dalvik cache
Format /system
Format /cache
Format /data media sdcard
Install rom
Install gapps
make sure your rom and gapps zip is in extsdcard, or else it will removed
be carefull not to format /extsdcard
above process will surely give positive results if done preciesely

150208 said:
what costum rom did you tried to install?
============
ROOT and update recovery:
HERE is the fastest way to root
reboot to recovery, and flash latest recovery again from HERE
reboot and go to recovery again.
Flashing roms:
Do a back up of important data/rom, place it inside your pc
Inside recovery:
Wipe data
Wipe cache
Wipe dalvik cache
Format /system
Format /cache
Format /data media sdcard
Install rom
Install gapps
make sure your rom and gapps zip is in extsdcard, or else it will removed
be carefull not to format /extsdcard
above process will surely give positive results if done preciesely
Click to expand...
Click to collapse
Thank you..
yas trying to install slimrom.. will now try out with cyanogen. . Will post how it goes soon..
UPDATE:
The above steps go well, till the rooting part..i installed twrp and rebooted into recovery to take backup.. the backup was sucesful.. the i booted into the rom to copy the backup files into my pc.. and tried to reboot it into recovery again.. and i again got stuck in the samsung logo screen..

akshaydogra said:
Thank you..
yas trying to install slimrom.. will now try out with cyanogen. . Will post how it goes soon..
UPDATE:
The above steps go well, till the rooting part..i installed twrp and rebooted into recovery to take backup.. the backup was sucesful.. the i booted into the rom to copy the backup files into my pc.. and tried to reboot it into recovery again.. and i again got stuck in the samsung logo screen..
Click to expand...
Click to collapse
For some reason this tab only works with Phils recovery.. for the rest. it just refuses to work.,! but the problem was that i could not get into the external memory card.. anyways.. after following the 'data wipe' instructructions.. i sideloaded cm-11-20140304-NIGHTLY-p3110.zip with its gapps..
both got installed succesfully.. However,, at first the tab went into a boot loop.. so i got into recovery again and cleared the data and cache partitions.. now.. i got stuck at a 'Blank' screen after the samsung logo.. ( its still blank after 10 mins)..

akshaydogra said:
For some reason this tab only works with Phils recovery.. for the rest. it just refuses to work.,! but the problem was that i could not get into the external memory card.. anyways.. after following the 'data wipe' instructructions.. i sideloaded cm-11-20140304-NIGHTLY-p3110.zip with its gapps..
both got installed succesfully.. However,, at first the tab went into a boot loop.. so i got into recovery again and cleared the data and cache partitions.. now.. i got stuck at a 'Blank' screen after the samsung logo.. ( its still blank after 10 mins)..
Click to expand...
Click to collapse
did it still blank? carefully not to flash with the charger on.
some people got bricked and to resolve that you must wait until the battery drops out and charge it again.
maybe you should clear your mind first, don't be in rush. i feel your frustating man :laugh:
if you do not add anything more in the process, i suppose with any recoveries you will succeed.
and also, it's a normal to take 10-15 min on the first boot

150208 said:
did it still blank? carefully not to flash with the charger on.
some people got bricked and to resolve that you must wait until the battery drops out and charge it again.
maybe you should clear your mind first, don't be in rush. i feel your frustating man :laugh:
if you do not add anything more in the process, i suppose with any recoveries you will succeed.
and also, it's a normal to take 10-15 min on the first boot
Click to expand...
Click to collapse
yeah brother.. i do feel frustrated this thing just wont work!! thank you for helping me out on this.. i really appreciate it..
i left it to completely drain the battery and then charge it again.. then it got stuck on the samsung logo and this time.. i did wait for 30 mins or so.. still nothing..
is there a rom you can suggest?? other than cyanogen?? il download that and try it.. i just want to get rid of the stock firmware..

akshaydogra said:
yeah brother.. i do feel frustrated this thing just wont work!! thank you for helping me out on this.. i really appreciate it..
i left it to completely drain the battery and then charge it again.. then it got stuck on the samsung logo and this time.. i did wait for 30 mins or so.. still nothing..
is there a rom you can suggest?? other than cyanogen?? il download that and try it.. i just want to get rid of the stock firmware..
Click to expand...
Click to collapse
mokee, omni rom, cm11 rom, i think they are stable enough with a great support, continuity constantly updates.
right now i'm use aosb, kind of loving the features

maybe broken EFS?

150208 said:
mokee, omni rom, cm11 rom, i think they are stable enough with a great support, continuity constantly updates.
right now i'm use aosb, kind of loving the features
Click to expand...
Click to collapse
ok.. il try out omni and aosb in order.. if omni works.. then omni it is.. ;p
Il post the results soon..

akshaydogra said:
yeah brother.. i do feel frustrated this thing just wont work!! thank you for helping me out on this.. i really appreciate it..
i left it to completely drain the battery and then charge it again.. then it got stuck on the samsung logo and this time.. i did wait for 30 mins or so.. still nothing..
is there a rom you can suggest?? other than cyanogen?? il download that and try it.. i just want to get rid of the stock firmware..
Click to expand...
Click to collapse
Maybe your EFS broken for some reason... that´s why it won´t boot into system.... you can try all roms, no rom will boot and you'll only see the samsung bootlogo...
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
also seems that it happens here too: http://forum.xda-developers.com/showthread.php?t=2657774

Android-Andi said:
Maybe your EFS broken for some reason... that´s why it won´t boot into system.... you can try all roms, no rom will boot and you'll only see the samsung bootlogo...
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
also seems that it happens here too: http://forum.xda-developers.com/showthread.php?t=2657774
Click to expand...
Click to collapse
Hi,
Thanks for jumping in.. i am new to this.. so how can i check if the EFS is broken??
i have GT-P3110_PhilZ-Touch-Recovery_6.19.6.zip as my recovery, i googled around and found that the official Clockwork build for p3110 does not support flashing of kit-kat roms.. and for some reason unknown to me,. this is the only recovery that works flawlessly..
which recovery do you suggest?? il go with that...

akshaydogra said:
Hi,
Thanks for jumping in.. i am new to this.. so how can i check if the EFS is broken??
i have GT-P3110_PhilZ-Touch-Recovery_6.19.6.zip as my recovery, i googled around and found that the official Clockwork build for p3110 does not support flashing of kit-kat roms.. and for some reason unknown to me,. this is the only recovery that works flawlessly..
which recovery do you suggest?? il go with that...
Click to expand...
Click to collapse
go to this thread http://forum.xda-developers.com/showthread.php?t=2548257
you will find the latest recovery

Mohdsultan said:
go to this thread http://forum.xda-developers.com/showthread.php?t=2548257
you will find the latest recovery
Click to expand...
Click to collapse
Thank you for this.. WIll try TWRP with Omni Rom today.. will post results in a while.. Right now at work

No Luck
I tried using GT-P3110_PhilZ-NON-Touch-Recovery_6.12.8_(Advanced-CWM).tar.md5 as recovery and flashed the omni rom as per instructions.. But the tab rebooted itself ones, and then got stuck on the samsung logo.. i dont understand what i am doing wrong.. sorry for acting like a total noob..
Please help out..

Android-Andi said:
Maybe your EFS broken for some reason... that´s why it won´t boot into system.... you can try all roms, no rom will boot and you'll only see the samsung bootlogo...
this got reported in a german forum, because 2 guys flashed CWM 6.0.4.4-Touch on the device... CWM 6.0.4.4-Touch not released for the Tab 2 - it was for a different device and flashing that recovery brokes EFS for them.
also seems that it happens here too: http://forum.xda-developers.com/showthread.php?t=2657774
Click to expand...
Click to collapse
Iv tried all the recoveries.. but the end result is always the same.. a tab stuck on samsung logo.. Please help out.. big noob here..

[Q] Failed upgrade - now soft bricked

Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim

sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989

thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?

sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989

yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.

No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim

sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989

good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.

Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim

sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989

Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app

[Q] after latest CM11 update, Galaxy Grand I9082 is stuck at boot screen

Hi guys,
Although this is my first post, I have been following xda-developers for a few years and have some experience installing custom ROMs.
I have a rooted Samsung Galaxy Grand Duos (I9082). I installed the custom rom developed by @pawitp using instructions in this forum. http://forum.xda-developers.com/showthread.php?t=2563557
I installed the "20140709" version of the ROM (https://goo.im/devs/pawitp/i9082_cm11.0/) successfully.
I was then able to upgrade to the next version (20140813) without requiring a data wipe.
I just saw that the 20140917 version has been released and flashed it using CWM.
But I see that the phone is stuck at the boot screen. I've already tried wiping cache/data before-and-after reflashing the zip. No luck.
I'd like some advice on how to proceed.

That newest update probably needs full wipe

Arch9 said:
That newest update probably needs full wipe
Click to expand...
Click to collapse
The dev's notes mention that a full wipe is not required, for the record.
As I mentioned, I did a full wipe i.e. deleted contents of /data.