I am having a strange situation that I switched on Bluetooth, then my Neo V went into a reboot loop.
I've modified framework-res.apk a few weeks before (to add usb storage), but everything's normal as normal until I switched on Bluetooth today and it crashed. It will boot into Android (again) and I can see the lock screen, before it reboots again.
I try to enter recovery and replaced the original framework-res.apk but still reboot loop. I then cleared cache and dalvik-cache, and the boot just after that is fine. I can use the phone after the dalvik-cache is rebuilt. But then when I reboot it went into a reboot loop again!!!
I try to use the PC Companion to recover, but I don't know if it is due to the pending update to .587 it didn't even want to recover.
Anyone have any idea how to fix it?
P.S. I am using .431 official, unlocked bl and rooted.
I'm experiencing the same on my Galaxy Nexus. Very annoying.
Unlocked why u asking questions take it as its fked flash any ROM to fix
Sent from my Xperia neo using xda premium
Well I know that this forum isn't for GNex but I'll still continue the discussion. It probably isn't a fked ROM as it happened on ICS as well as JellyBean. Both the time I tried switching the BT on via Notification Toggle.
Yer I heard of it before more like missing pngs or error in compile or something just flash different ROM
Peace chris
Sent from my Xperia neo using xda premium
Same thing on HTC HD2
kormatoes said:
Yer I heard of it before more like missing pngs or error in compile or something just flash different ROM
Peace chris
Sent from my Xperia neo using xda premium
Click to expand...
Click to collapse
I'm having the same problem on HTC HD2 with Tytung's JB v1.3a. Turned on BT in Notification box and is now bootlooping. Doesn't even get to lockscreen, just stuck in Cyanogenmod 10.
Can't find any solution on XDA other than the above. Flash new rom or factory reset. I read on another thread (In which I can't publish because I'm a new user) someone has the same problem with an HD2 on tytung's ICS. Could this be hardware related?
Anyone can offer a permanent fix for BT bootloop?
I have tried the following:
re-flash mod with Dalvik wipe (doesn't work)
wipe Dalvik and /cache from CWM (doesn't work)
Now re-flashing rom with factory reset. :crying:
If you find a solution for it then please inform me too.
Sent from my Galaxy Nexus using Tapatalk 2
Goto CWM & wipe delvik cache, then reboot ur phone.. For permanent solution flash stock rom with full wipe..
Sent from my Xperia neo V using Tapatalk 2
Try to replace your Bluetooth.apk
From stock Rom
Give permissions!
Do this once you do a clean install and post results!
Maybe the Bluetooth gets corrupted!
So I suggest try above solution
Sent from my MT11i using xda premium
Samak46 said:
Goto CWM & wipe delvik cache, then reboot ur phone.. For permanent solution flash stock rom with full wipe..
Sent from my Xperia neo V using Tapatalk 2
Click to expand...
Click to collapse
The problem used to occur with stock ICS and stock jellybean too.
Sent from my Galaxy Nexus using Tapatalk 2
AbhishekS said:
The problem used to occur with stock ICS and stock jellybean too.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try the fix I suggested?
Sent from my MT11i using xda premium
AbhishekS said:
The problem used to occur with stock ICS and stock jellybean too.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This is the solution for Xperia neo V, many users had this problem & solved through this method
Sent from my Xperia neo V using Tapatalk 2
Ghostfreak NB said:
Did you try the fix I suggested?
Sent from my MT11i using xda premium
Click to expand...
Click to collapse
I just have to replace the apk, right?
Well I just activated bluetooth and it's working fine. I haven't replaced the APK yet. The problem is that most times bluetooth works fine but sometimes it goes to a bootloop.
Even if I replace it, I won't be able to confirm whether the problem is fixed or not.
Sent from my Galaxy Nexus using Tapatalk 2
AbhishekS said:
I just have to replace the apk, right?
Well I just activated bluetooth and it's working fine. I haven't replaced the APK yet. The problem is that most times bluetooth works fine but sometimes it goes to a bootloop.
Even if I replace it, I won't be able to confirm whether the problem is fixed or not.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yup,change the apk now! And then try to reboot phone
Or else
Open Rom zip
Go to system /app
Replace Bluetooth with stock Bluetooth file
And try to reboot!
Sent from my MT11i using xda premium
BTW from where can I get the stock Bluetooth.apk? Even AOSP isn't stock, and the real stock ROMs are IMG files.
Sent from my Galaxy Nexus using Tapatalk 2
AbhishekS said:
BTW from where can I get the stock Bluetooth.apk? Even AOSP isn't stock, and the real stock ROMs are IMG files.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Copy stock rom to pc, open the img file using winrar, goto system/apps folder & extract the bluetooth.apk
Sent from my Xperia neo V using Tapatalk 2
Samak46 said:
Goto CWM & wipe delvik cache, then reboot ur phone.. For permanent solution flash stock rom with full wipe..
Sent from my Xperia neo V using Tapatalk 2
Click to expand...
Click to collapse
For me wiping dalvik cache doesn't help. Only a factory reset gets my phone working again.
Samak46 said:
Copy stock rom to pc, open the img file using winrar, goto system/apps folder & extract the bluetooth.apk
Sent from my Xperia neo V using Tapatalk 2
Click to expand...
Click to collapse
Thanks. But are you sure that the IMG files can be opened using Winrar?
Sent from my Galaxy Nexus using Tapatalk 2
AbhishekS said:
For me wiping dalvik cache doesn't help. Only a factory reset gets my phone working again.
Thanks. But are you sure that the IMG files can be opened using Winrar?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Use power iso! For Img files
But I'm not sure why you need to open the file
N by stock,I meant the files which you get with Rom while you buy a phone!
Sent from my MT11i using xda premium
Well actually the problem existed on stock ROM too. And you know that the stock of a Galaxy Nexus indeed means pure stock!
Sent from my Galaxy Nexus using Tapatalk 2
Did it happen even after doin factory reset?
Or else, it could be a hardware defect!
Sent from my MT11i using xda premium
Related
i made a new rom from kitchen. First i tried to flash it with only root and busybox and it worked. After that i tried to deodex the app and framework files and then i flashed it. It installed successfully but m stuck on the start screen.It shows "Samsung Galaxy Y gt-s5360" this is the screen which comes before the bootanimation screen. Its stuck on it for the past half an hour!!
Go to downloading mode and flash a cwr with odin then flash a good NONCOOKED by YOU rom!!!
Press thanks if I was of any help!...
Sent from my GT-I5500 using Tapatalk 2
It could be that you didn't wipe. But did you use cwr? I would say it was a bad flash is all.
Sent from my Incredible using XDA
Btw prince that is not a very nice post. Everyone starts somewhere, and optimizing stock roms is a great way to maintain stability.
Sent from my Incredible using XDA
prince147 said:
Go to downloading mode and flash a cwr with odin then flash a good NONCOOKED by YOU rom!!!
Press thanks if I was of any help!...
Sent from my GT-I5500 using Tapatalk 2
Click to expand...
Click to collapse
Guess your post wasn't much helpful lol
Sent from my HTC One X using xda premium
MKe sure you wipe sTar and cache. Also wipe /system and /boot.
Sent from my Incredible using XDA
Hello guy im having some issues installing omega v12 to my gs3 my phone is GT-I9300 model and rooted, I downloaded the room to my internal sdcard and install it via cwm, the installation secced every time but when it reboot it gets stuck at samsung logo and returns to recovery, whats wrong with my phone? or what am I doing wrong?
Anyone pls.!!!!!:crying::crying::crying::crying:
Have you wiped it before flashing the Rom e.g. factory reset wiped cache and delvik cache also they flashing it twice straight after each other
Sent from my GT-I9300 using xda premium
There should be no need to install it twice in a row. Try what was first suggested.. when in recovery, wipe data/ factory reset, wipe cache, wipe dalvik, flash ROM... reboot.
Did you make a nandroid backup before flashing?
Sent from my Galaxy Nexus using xda premium
Coreym said:
There should be no need to install it twice in a row. Try what was first suggested.. when in recovery, wipe data/ factory reset, wipe cache, wipe dalvik, flash ROM... reboot.
Did you make a nandroid backup before flashing?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yup I did all wipe and flash ROM, the Rom flashes perfectly, when it reboots goes to samsung logo twice, than it send me again to recovery mode, and yes, I made a nandroid backup, but its not working, im flashing criskelo ROM to see if it works. Any other Ideas?
Thanks for youre reply!
Keymab said:
Yup I did all wipe and flash ROM, the Rom flashes perfectly, when it reboots goes to samsung logo twice, than it send me again to recovery mode, and yes, I made a nandroid backup, but its not working, im flashing criskelo ROM to see if it works. Any other Ideas?
Thanks for youre reply!
Click to expand...
Click to collapse
Bummer. Yeah flash another ROM if you have it on your SD card.. try to boot into something. If it was a bad DL of the omega rom it shouldn't flash, and the fact that your getting successful is weird
Next step is maybe pushing a files onto your phone via ADB and try to flash again. You got recovery so your not too bad off
Sent from my Galaxy Nexus using xda premium
Coreym said:
Bummer. Yeah flash another ROM if you have it on your SD card.. try to boot into something. If it was a bad DL of the omega rom it shouldn't flash, and the fact that your getting successful is weird
Next step is maybe pushing a files onto your phone via ADB and try to flash again. You got recovery so your not too bad off
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Guess what? Ive just install Criskelo ROm and it worked!! maybe omega ROM is wrong, I really wanted to try it, About criskelo ROM I went here http://forum.xda-developers.com/showthread.php?t=1714091 but no kitchen option appear, I installed normally and I rebooted, what do I have to do?
chek ur md5 of omega rom .. it must be bad download .. its happens when u flash bad downloaded file so always chek md5 before flashing any rom .. nice habit to chek
Sent from my GT-I9300 using xda premium
hisee said:
chek ur md5 of omega rom .. it must be bad download .. its happens when u flash bad downloaded file so always chek md5 before flashing any rom .. nice habit to chek
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Checked, and its the same md5, anout criskelo I downloaded the full ROM not the kitchen!!! LOL
Keymab said:
Checked, and its the same md5, anout criskelo I downloaded the full ROM not the kitchen!!! LOL
Click to expand...
Click to collapse
then try again. wipe data wipe cache wipe dalvik and flash omega it will work if its nt a bad download
Sent from my GT-I9300 using xda premium
Another question, I came from a Gnex and there I knew all ROmS, about gs3 I know nothing, so, whats the best room right now? Omega, Criskelo? I like touchwiz Rom.
see its depen upon u what u want ...looks with good battery (omega)or stock exp (check rom)or very good battery(rgui)..
Sent from my GT-I9300 using xda premium
Damn phone, I just Install criskelo kitchen ROM and I got stuck on samsung screen!! Maybe something is wrong with my s3, i just could install criskol full rom and thats it!!
Keymab said:
Damn phone, I just Install criskelo kitchen ROM and I got stuck on samsung screen!! Maybe something is wrong with my s3, i just could install criskol full rom and thats it!!
Click to expand...
Click to collapse
u have gt i9300 only na. ??? or other version?
Sent from my GT-I9300 using xda premium
---------- Post added at 07:58 AM ---------- Previous post was at 07:57 AM ----------
insll latest cwm. or cf root .
Sent from my GT-I9300 using xda premium
hisee said:
u have gt i9300 only na. ??? or other version?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yup, GT-I9300.Ill try to post a video.
Maybe you can try formatting your system partition.
Sent from my GT-I9300 using xda app-developers app
Arsaw said:
Maybe you can try formatting your system partition.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Done. Still the same. It wont boot
Mi stock firm its XXXXALFE something, does it has to do with it?
as I said try to flash latest cf root and flash rom
Sent from my GT-I9300 using xda premium
hisee said:
as I said try to flash latest cf root and flash rom
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I root it with cf-6.4 is that the latest?
Also re-rooted again, and no luck.
Hi all, sorry if this has been posted before, i cant seem to find links to such problem. Ive flashed sony tablet s from 4.0.3 release2(rooted) to 4.0.3 release 1a (done wipe data before flash stock 1a), rooted the tab using condi's 5.2, and later using condi's custom pre-rooted release r5.. All went well, tab upgraded to r5. Problem is whenever i reboot the tab, it goes back to 4.0.3 release2 and vice versa. Tested it a few more time to see if sticks to one fw but it switches from release2 to r5 every single reboot.. Help anyone? Thanks...
Sent from my GT-N7000 using Tapatalk 2
These are screenie from both r2 n r5 after each boot.. Build prop differ too.. Both fw booted in full root mode and no other error only titanium backup seem to close after each reboot..
Sent from my GT-N7000 using Tapatalk 2
Nazwany said:
These are screenie from both r2 n r5 after each boot.. Build prop differ too.. Both fw booted in full root mode and no other error only titanium backup seem to close after each reboot..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Interesting and awesome in the same time
Sent from my Sony Tablet S using xda premium
Haha would be more interesting if dual boot from cm9 to stock ics... Right now its a bit annoying if the batt dies or u need a quick reboot.
Sent from Galaxy NoteZ RR12
Nazwany said:
Haha would be more interesting if dual boot from cm9 to stock ics... Right now its a bit annoying if the batt dies or u need a quick reboot.
Sent from Galaxy NoteZ RR12
Click to expand...
Click to collapse
Yeah, it is possible but you wouldn't be able to choose which partition and plus, Sony still has not unlocked the bootloader while the other Sony devices get there bootloaders unlocked. :sly:
Sent from my Sony Tablet S using xda premium
So is there any way for now i can format one of thr partition with the r2 fw and just boot on r5?
Sent from Galaxy NoteZ RR12
Nazwany said:
So is there any way for now i can format one of thr partition with the r2 fw and just boot on r5?
Sent from Galaxy NoteZ RR12
Click to expand...
Click to collapse
Problem, bootloader still locked.
Sent from my Sony Tablet S using xda premium
Well guess im stuck here then haha.. Look on the bright side ive 2 rooted fw to mess ard wit haha.. Thanks alot...
Sent from Galaxy NoteZ RR12
I have a similar problem too. I had the same firmware on both though, but only had root on one. This was how I noticed it. My only solution was to delete the system folder on the second partition. Now I get a boot loop every second power cycle.
Glad to hear I'm not the only one. Maybe it's the beginning of a dual boot system
Sent from my Sony Tablet S using XDA Premium HD app
Wat fw were u on on both partition? i was tinking of flashing the partition with r2 with the latest update But the locked bootloader hold me back cos i might just flash over the partition with the r5.. What i was Confused about is the kernel cos seems both fw have diff kernel version.. Does that like means something or its just the fw loaded with the kernel it came with..
Sent from Galaxy NoteZ RR12
Just noticed condi released custom prerooted r5a! And with double flash... Cant wait to try out tat just have to wait for wifi version to be released..
Sent from Galaxy NoteZ RR12
[Never Mind... I think I have a different glitch]
defsix said:
I have a similar problem too. I had the same firmware on both though, but only had root on one. This was how I noticed it. My only solution was to delete the system folder on the second partition. Now I get a boot loop every second power cycle.
Glad to hear I'm not the only one. Maybe it's the beginning of a dual boot system
Sent from my Sony Tablet S using XDA Premium HD app
Click to expand...
Click to collapse
Try reseting via recovery a few times until you end up in System partition 1.
Sent from my Sony Tablet S using xda premium
I did a factory reset in both partitions. I think I tried it in recovery too. It's working ok for now. It's stopped messing up my apps, I'll also know if it's rebooted itself because it will be stuck in boot loop. Since I upgraded to R5 it hasn't crashed once.
Sent from my Sony Tablet S using XDA Premium HD app
Hey everyone was wondering of I could get a hand. I recently got a Samsung galaxy player 5.0 US version. I have it rooted and cwm recovery installed. When I try to flash a Rom I get a status 7 error is there a way to fix this. Also my capacitive buttons have stopped working as well . Any help will be appreciated, thanks
jdaub89 said:
Hey everyone was wondering of I could get a hand. I recently got a Samsung galaxy player 5.0 US version. I have it rooted and cwm recovery installed. When I try to flash a Rom I get a status 7 error is there a way to fix this. Also my capacitive buttons have stopped working as well . Any help will be appreciated, thanks
Click to expand...
Click to collapse
This should have been posted in the q&a.
Also try to redownload the zip and try to wipe /system
Sent from my YP-G1 using Tapatalk 2
goldflame09 said:
This should have been posted in the q&a.
Also try to redownload the zip and try to wipe /system
Sent from my YP-G1 using Tapatalk 2
Click to expand...
Click to collapse
By wipe system do you mean format it. I think the only thing that I can specifically wipe is data,dalvik cache,and cache
jdaub89 said:
By wipe system do you mean format it. I think the only thing that I can specifically wipe is data,dalvik cache,and cache
Click to expand...
Click to collapse
By that I mean
Recovery - mounts and storage - format system
Sent from my Kindle Fire running CM10.1/SGT7
Ok I did that and I still get the error it happened with Pac man Rom and paranoid android downloaded the US version. Which is what I have. I've flashed things before on my one x and nexus 7 and never had a problem so I'm lost. I attached a picture of the error message
Sent from my HTC One X using xda app-developers app
jdaub89 said:
Ok I did that and I still get the error it happened with Pac man Rom and paranoid android downloaded the US version. Which is what I have. I've flashed things before on my one x and nexus 7 and never had a problem so I'm lost. I attached a picture of the error message
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Flash jellybean 4.1 first then install cm 10.1.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Flash jellybean 4.1 first then install cm 10.1.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
actually, i think he has to flash cm9 first, because some users experienced the same problem going from gb to 4.1
iurnait said:
actually, i think he has to flash cm9 first, because some users experienced the same problem going from gb to 4.1
Click to expand...
Click to collapse
im gonna have to agree with that one cause i have someone with the same problem. told him to go to cm9 and he said he could get on cm9 but not cm10 from gb
That worked out perfectly thank you very much!!
Sent from my HTC One X using xda app-developers app
I had the same problem with the keys not working. Do you know how to fix that?
Sent from my SCH-I535 using xda app-developers app
Can anyone help me? My phone reboots when I power it up. I use latest phantom kernel with stock Rom. So, I hold the power button, the phone turns on, I see the phantom kernel logo, then I see the Xperia logo, it kinda blinks for a second, when it reappears it does it again, then it continues for 2 seconds, I see the Sony waves thingy, the same thing happens 2-3 times, then it reboots and loads as if nothing happened!(or it does it again 1 more time)
The weird part is that it was alright a few days ago but this thing has scared the heck out of me! Help me pls!
Sent from my ST27i using xda app-developers app
That's the rom bootlooping. It could be caused by any problem. If it finally boots then it should not be a problem. (but I guess you should backup your data if problem increases (I suggest using Onandroid as you can make full nandroids without booting into recovery)) alternatively you can try to remove your int.d scripts and see if it helps. But make a nandroid before trying anything)
Sent from my LT22i using XDA Premium 4 mobile app
What do you mean init.d scripts? I don't even know what they are, I only know that I enabled init.d support from pimp my Rom app...
Sent from my ST27i using xda app-developers app
OverdiveKill said:
What do you mean init.d scripts? I don't even know what they are, I only know that I enabled init.d support from pimp my Rom app...
Sent from my ST27i using xda app-developers app
Click to expand...
Click to collapse
I believe the Phantom kernel has init.d support built-in.
You can check to see if you have any init.d scripts in /etc/init.d with Root Explorer or FX file manager with FX Root Access or any file manager that can access the root fs.
Can you still go to the home screen? If not, the best bet is that you need to re-install the ROM. Bootloops happened to me many times while playing with my Xperia, installing custom fonts, and due to that I never got scared of bootloops anymore cause I can always revive my Xperia.
Install the ROM again if you experience bootloops. Cheers
No I can still use it after 1 or 2 bootloops
Sent from my ST27i using xda app-developers app
OverdiveKill said:
No I can still use it after 1 or 2 bootloops
Sent from my ST27i using xda app-developers app
Click to expand...
Click to collapse
reflashing will help... reflash stock rom then reflash phantom kernel then clear dalvik cache and normal cache.. or you could flash a new rom.. try @prototypell's powerJB rom.... its brilliant
suyash691 said:
reflashing will help... reflash stock rom then reflash phantom kernel then clear dalvik cache and normal cache.. or you could flash a new rom.. try @prototypell's powerJB rom.... its brilliant
Click to expand...
Click to collapse
Why powerJB and not a newer rom? Any advantages?
OverdiveKill said:
Why powerJB and not a newer rom? Any advantages?
Click to expand...
Click to collapse
because it is the most stable and bugfree rom .... superjb is bloated with xperia z **** like illumination bar and other stuff (eats 50 mb ram and isn't valid fr our phone) .... i hvnt tried beanZ, u can try