I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
jhr5474 said:
I have a p5113 and it is running 4.2.2 it is a friends. It turns on all the way to the homescreen for about 30 seconds. Then it reboots. I have gotten into recovery and it lets me wipe data factory reset. Then when I go to reboot it shows an error below the android and there has been no data wipe when it reboots. and reboots and reboots.........It also says NO COMMAND when booting recovery below the android. OH, I also tried flashing another stock recovery. Did not fix issue with recovery.
I have gotten into download mode and tried to cf root. Doesnt work, no recovery. Still same as above just goes to stock with no command written at bottom then error when you go to reboot it. Tried both versions of CWM and TWRP Odin files. DONT WORK. Tried to flash recovery by zip and get signature verification failure.
I figured oh, I will do what I always do to tablets try and reinstall the firmware. Which is the 4.2.2 firmware I go ahead and odin it, everything looks fine, it did take way too long like an hour and half. Passes, reboots, same operating system same data didnt change a thing! Still rebooting still recovery errors. Tried to downgrade to ICS and it passed after an hour and a half of slow odining NOTHING again same story as JB didnt change anything.
I have noticed that there is an avg in apps. I never get enough time to uninstall it. It always reboots before I can get to it. ANY HELP IS APPRECIATED.
Click to expand...
Click to collapse
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
yep its
aditya rathee said:
so you wanna say that your tab is in bootloop
if that then please revert to stock rom
also if you are not able to do this then i have to say that your tab is bricked
try triangle away or take it to customer care
Click to expand...
Click to collapse
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
jhr5474 said:
not a brick and I am on stock if you would have read the OP you would know that. I have had a brick before the definition of a brick is a device that does not turn on. I have flashed many tabs with stock and customs. Thanks for the great advice but I am a member of XDA and I like to do things myself or with the help of others in my community. I REFUSE TO TAKE ANY ANDROID DEVICE TO CUSTOMER CARE THAT STILL TURNS ON>
Click to expand...
Click to collapse
i like your confidence brother but i was just helping you
also with your threads title in thought you were still having bootloop
also boot loop mainly happens when system files interfere with each other and result in instability during boot and crashes also it is not always necessary that in boot loop device would not turn on as you said earlier
i have seen boot loop on my tab even during charging animation as it was off it was due to use of flashing scripts that conflicted with each other
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
corrosivefrost said:
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
Click to expand...
Click to collapse
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
buhohitr said:
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
Click to expand...
Click to collapse
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
corrosivefrost said:
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
Click to expand...
Click to collapse
I know for a fact that there has been issues with the flashing of 4.4 and encryption. The best bet is to turn encryption on then off again. Now you said you never encrypted it but the Turn it on then off again approch might work here. I also know for a while TWRP had issues flashing 4.4 so it might be worth it to run CWM.
Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.
Wokeup this morning and decided to restart my phone as i usually do every morning, but after the restart the phone has remained in safe mode since then. I have tried restarting the phone several times to no avail.
I believe phone has been rooted about 2 years ago or so. I dunno what kind of recovery im running also.
I am still running 5.1.1
J700HXXU1AOG6 (baseband version)
LMY48B.J700HXXU1AOI3 (build number)
Please any help to resolve this would be greatly appreciated
NOTE:
Im a noob, so please try to be clear as possible.
THANKS
UPDATE
Just realized the volume down button is not working(clicks but doesnt lower the volume). So im guessing this is what makes it enter safe mode all the time
What recovery are you using?
souvikghosh915 said:
What recovery are you using?
Click to expand...
Click to collapse
Well im not too sure, but when i was factory resetting the phone some blue/dark screen showed with TEAM WIN underneath it
Ekwere said:
Well im not too sure, but when i was factory resetting the phone some blue/dark screen showed with TEAM WIN underneath it
Click to expand...
Click to collapse
You have backups ?
What kind of ROM are you using ?
Anyways best is gonna be download any rom and wipe system, data, cache, dalvik...then flash it.
If you don't have backup and you're on stock then just download the firmware from Sammobile and then flash it via Odin, remember don't factory reset, else your all data will be wiped out.
Then start your phone, take a backup of the things you'll need and then reset and flash it again.
And if you're on a custom ROM and you don't have backups then flash the ROM on your recovery again without wiping anything. Restart your device then, you'll see your datas intact, then take a backup but most likely you'll see a lot of force stops of several apps while in this process. Then complete by flashing it again after wiping data system cache dalvik.
souvikghosh915 said:
You have backups ?
What kind of ROM are you using ?
Anyways best is gonna be download any rom and wipe system, data, cache, dalvik...then flash it.
If you don't have backup and you're on stock then just download the firmware from Sammobile and then flash it via Odin, remember don't factory reset, else your all data will be wiped out.
Then start your phone, take a backup of the things you'll need and then reset and flash it again.
And if you're on a custom ROM and you don't have backups then flash the ROM on your recovery again without wiping anything. Restart your device then, you'll see your datas intact, then take a backup but most likely you'll see a lot of force stops of several apps while in this process. Then complete by flashing it again after wiping data system cache dalvik.
Click to expand...
Click to collapse
No, i dont have any backups(most things were saved on SD card)
I believe its stock rom. The only thing i remember doing is rooting the phone long time ago when i got it.
I just realized that the volume down button is not functioning(clicks in but doesnt lower the volume) and i believe this is where the issue is as the volume down activates the safe mode feature
Im still gonna flash the phone none the less cos im still on older android and i hope it works
That volume down button is broken, stuck ON. Get it fixed.
Sent from my SM-J700M using Tapatalk
Thanks a lot to everyone who tried to help.
Will be taking the phone for repairs by Monday and will drop a feedback on how that goes
Fixed the volume down button and the phone is back to normal now.
Time to close this thread and go search on how to root the 6.0.1
Thanks guys
Cheers!
Sent from my SM-J700M using Tapatalk
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
I'm still stuck in this situation...
Any help plz?
IYaWonaRoo said:
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
Click to expand...
Click to collapse
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
savagevegeta said:
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
Click to expand...
Click to collapse
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
IYaWonaRoo said:
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
Click to expand...
Click to collapse
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
savagevegeta said:
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
Click to expand...
Click to collapse
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
IYaWonaRoo said:
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
Click to expand...
Click to collapse
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
savagevegeta said:
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
Click to expand...
Click to collapse
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
IYaWonaRoo said:
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
Click to expand...
Click to collapse
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
savagevegeta said:
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
Click to expand...
Click to collapse
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
IYaWonaRoo said:
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
Click to expand...
Click to collapse
The steps to fix storage 0mb are clearly posted in the TWRP thread.
ashyx said:
The steps to fix storage 0mb are clearly posted in the TWRP thread.
Click to expand...
Click to collapse
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
IYaWonaRoo said:
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
Click to expand...
Click to collapse
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
ashyx said:
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
Click to expand...
Click to collapse
I probably was doing it wrong lol. But its fixed now so dont worry
IYaWonaRoo said:
I probably was doing it wrong lol. But its fixed now so dont worry
Click to expand...
Click to collapse
Your data partition will still be unmountable and remain 0mb, which means you are unable to make a backup.
However if you're happy with it in that state...
Re: bootloop
have you tried grabbing the no verity/encrypt form the rooting forum, this solves seandroid problem