Database Develop

[Q] Stuck in bootloop - What should I do?

Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961

Hi there,
Bootloops happen every now and then, if something collides or is misconfigured.
In my very own experience most boot loops happen to be script related.
This is why you should´t worry too much.
You still can enter CWM?
If so enter CWM and wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If it still is in boot loop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodels which slightly differ from original)
In case you do not have a rooted device without CWM only thing you can do, is to begin from scratch by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device including you´ll keep all your private stuff.
Flashing the Samsung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #

DJ-Tumor said:
Hi there,
Bootloops happen every now and then, is somethine collides or is misconfigured.
In my very own experience most boot loops happen to be skript related.
This is why you should´t worry too much.
You still can enter CWM?
If so Enter CWM, wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If ist still is in bootloop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodel which slightly differ from originall)
In case do not have a rooted device without CWM only thing you can do, is to begin from scrath by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device incl. you keep all your private stuff.
Flashing the Sasmung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
Click to expand...
Click to collapse
Have done as you said, but still problems.
One of the problems maybe can be that it isn't CWM but RedPill.
Yes, I did download the whole file, so no strange abort of the download.
And this is the correct ROM for the Galaxy Note.
If I still have this problems in 24 hours I will contact my store and let them know what I think. I want my money back. I can also add that I'm studying law, so I let the lawbook speek for itself.
But thanks for a fast answer!

Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of

DJ-Tumor said:
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
Click to expand...
Click to collapse
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?

MinnesotaVikings1961 said:
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Click to expand...
Click to collapse
You need to flash rocket rom v20 before v22 that i belive is or problem if u can mount sdcard to computer u may have to take sdcard out of your phone and put in something else to load the program on the card then put back on phone and then flash v20 of rocket rom and then see if it boots up if it dose then u can flash v22
Sent from my GT-N7000 using XDA Premium HD app

Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?[/QUOTE]
U could in download mode with odin pc
Sent from my GT-N7000 using XDA Premium HD app

Quick google search shows boot loops are pretty well known with this rom.
No you only can flash original rom with odin.
If there are important data on the device connect it cia usb and boot into cwm.
Now wath what happens. If you´re lucky mass storage mode is enables in the kernel and you got your storage mounted automated.
If not it´s time to cross fingers and search for an option to mount by hand.
I´m completely new to NOTE - all my knowledge comes from my i9000 which is a mega active community compared to the one of the NOTE
There is have the choice between 5 different ICS kernels alone
Each one has it´s abilities, so does one have the option to mount storage by hand.
This option can be found in "advanced". Hope this menu option is present in your rom
good luck!
# Rodger #

MinnesotaVikings1961 said:
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
Click to expand...
Click to collapse
Yeah you can. Just go to this thread. Get a rootable rom downloaded. Just follow the instructions to the word of how to flash via odin. And you will have stock rom. And you can again root and install custom rom!! No need to run back to store !
Links-
Roms and guide- http://forum.xda-developers.com/showthread.php?t=1424997
Rooting and odin - http://forum.xda-developers.com/showthread.php?t=1329360

Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?

chasmodo said:
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
Click to expand...
Click to collapse
Well, I had been using ICS MidNote for a short time, due to a friend mine wanted to see ICS for the Note.
Now I tried to get back to my regular GB ROM.
/ Jimmy

You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6

chasmodo said:
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
Sorry for being confusing you!
Before this bootloop I was running MidNote V2.0, ICS. I then tried to flash ROCKET ROM, V22. And when I started up, this bootloop came up, and isn't solved in writing moment, very many hours later.
/ Jimmy

Case closed
I can now say that the case is closed. What I did is very simple. In fact, so simple I never thinked about it. The only thing I did was to unroot my phone using Odin.
But thanks for all tips and support!
/ Jimmy

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

[Q] (NEED HELP) Phone restart itself into recovery after installing ICS/JB ROM's

Hi Seniors,
This became like a mystery for me..please help me to solve it.
Issue is like this if I install any custom or stock Gingerbread ROMS by phone works like a butter, no issue at all I can say.
But when I install any ICS or JellyBean ROM's it starts creating pain in my neck.
If I am using my phone it never restarts itself but when I lock my phone screen and keep it my pocket M finding that my phone is restarting into recovery mode itself.
Now here comes the strange part...If I play music using any music player and lock my screen it works fine,its not restarting itself ...but once I stop that music player and lock my handset screen in idle mode it goes to recovery in few secs
This only happens if I upgrade to ICS or JellyBean ROM's
One more issue...my wifi works fine If am having GingerBread install on my phone but when I install ICS/JB I cant even start it.
Have tried a lot to get it fixed....but
.....Even I want to taste ICS/JB Rom's like u guys...Please Help Your Rookie.
Thanks & Regards
D.J XactiX
Proud owner of Samsung Galaxy S i9000
----------------------------------------------------------------------------------------ANDROID ROCKS---------------------------------------------------------------------------------------------

Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you

EwOkie said:
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
Click to expand...
Click to collapse
Hey EwOkie,
Thanks for your courtesy mate...really appreciate it,
So here we go,
I had stock GB 2.3.6 ROM installed on my phone ;ie GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip,
after that I rooted my phone using CF-Root-XX_OXA_JW4-v4.4-CWM3RFS,
then I did factory reset,wipe cache and dalvik cashe and installed GamerzRom v11.0 which is a GB ROM,
so far no issue...wifi is working fine,phone is not at all giving me any auto restart issue...its was working like a charm,
then I found ICS_F4k_MOD_v4.0.4_I9000_r3.zip which is an ICS ROM,
I did factory reset,wipe cache and dalvik cache,the I installed ICS_F4k_MOD_v4.0.4_I9000_r3.zip using CWM Recovery console,
it was booted fine to home screen...later on I tried connecting my phone using my wifi router I found that WiFi was not switching on at all,
I locked my phone using lock button then after few secs I am finding my phone is restarting itself in recovery mode,
restarted my back to normal and again the same issue,
I ignored it,
Then I downloaded C-RoM Mix v7 Latest 4.2.1.zip in which had a wifi bug fix,
I did factory reset,wipe cache and dalvik cache,
I flashed it using clockworkmod recovery and had eactly that same issue which I had on ICS ROM,
for WIFI issue I tried flashing wififix.zip and found no resolution,
my phone went into boot loop of Samsung Logo,
then I flashed it back to original stock rom GB 2.3.6 and my phone started working like the way it should be.
This is the whole story
I moved from GB to ICS and then to JB.
Seriously brother I have no idea why its causing this weird issue...this is why I am looking for help from AndroidXperts on XDA site
Kindly help me to sort it out.
Thanks & Regards
D.J XactiX

Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask

EwOkie said:
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
Click to expand...
Click to collapse
Hi EwOkie,
Thanks for sharing your experience.
I am followed everything what u just mentioned in ur reply allready...but no go
Me & my GF we both have i9000 and I have followed same installation process on both the phones...her phones works like a charm but mine is like an incomplete soul.
One more thing mate,I really dont understand this ......can you tell me what difference it makes to have JVU 2.3.6 or some other version...how exactly its works....u know what I mean to say.

No idea why we use 2.3.6 JVU with CF Root (Kernel for Recovery) we just do ,, suppose its the best to start with before flashing a Custom Rom
So your partners phone works ok and yours doesnt.. did you try using the PIT File and re-partition?
Check my signature at bottom its a HOW TO Guide incase you get lost
As I says I dont have a lot of experience with ICS or JB Roms as the ones i flashed in the past werent as stable and had some bugs in them
Thats why i stuck with GB Roms

plz help me
today i install a custom rom lollipop in sony xperia c3 dual
but now my phone refused to start even same issue recovery mode... now my phone completely death.. when i try to start it red +green blink but fast mode work easily .. & when i connect my phone to charger it restart it self again & again ... its show only sony logo and its restart again ..plz help me

Can't Install Roms HELP PLEASE! Huawei U9000 Problems!

Hi I am new to this "romming" business. For my u9000 I installed UtterChaos kernel .32. Most to the roms require .35 kernel. And when I try to install SUT LR 1.8 it never works with windows 8 64 bit. I do have CWM Recovery, and I do have superuser permissions. But for some reason when I try to flash a different kernel like CK Kernel Lebay edition, the whole device gets stuck at boot. Yes I have wiped data, cache and davlik. before doing so. I had to then remove the batteries and put them back to start the phone in download mode to replace the boot image from a back up then go do a CWM restore. And I have tried doing factory resets but the UC kernel boot wont change.
Bottom line is, I AM LOST and I will be using this phone for a long time and I can use a way out of this and I need to find a very fast and stable rom with all working features.
What I have:
- .32 kernel
- UtterChaos kernel
- Custom SU
- CWM Recovery
What I need (please help):
- To get rid of UC kernel (boot, etc...)
- .35 kernel (if possible)
- SUT LR for Windows 8 64bit (if possible)
- A really good rom for heavy gaming, performance, stability, something other than GB (preferably JB or ICS)
I may be asking for too much, and sorry if I am, but I can use some help with this phone right about now.
Thanks in advance!

My answer
You can get 35.7 kernel here, depending on what rom you wish to use. Just flash it along with your preferred rom.
http://forum.xda-developers.com/showthread.php?t=1919097&highlight=kernel
For the rom, it really depends on your preference, because the performance is mostly the same between all the JB roms, smooth enough if you don't install lots of apps that stay in the background. Currently, I'm using the XperienceXperia JB rom. It's about as good as the other JB roms, just with Xperia stuff. Also, make sure that you don't put too much load on it, because it might freeze. No kind of software would be able to magically turn our phone into a gaming powerhouse, because it has an old, outdated gpu to start with. So, don't think about running games like Asphalt 8, because it probably wouldn't run.
http://forum.xda-developers.com/showthread.php?t=2479460
I'm not aware of a Win8 x64 compatible SUT LR, but I don't think you'd need it for anything besides flashing stock roms.
By the way, what rom are you using now? If you flash a cm10 (JB) designed kernel to a GB rom, it would definitely cause problems.
Sorry for the long reply, I don't know how to make it simpler.

THANKS
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?

2nd answer
_ikhan_ said:
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?
Click to expand...
Click to collapse
I'm not sure about the order myself, but I usually flash the rom first, then the kernel. I do this everytime I want to flash a rom, and I've never had any problems. Have you tried flashing one of the JB roms for this device? If you haven't tried, remember to wipe data and cache before flashing the rom, and backup your current rom just in case something goes wrong.

[Q]Flashing the same rom makes the device unusable

Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.

darkkfruit said:
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
Click to expand...
Click to collapse
I use Philz recovery and before flashing a new rom i just simply hit Clean up to install a new rom.
I never faced any of the issue that u mentioned. Try following what i said.
If u are using a lollipop rom then u may face systemui FC ,reboots as there is a bug which is experienced by some users.

I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.

darkkfruit said:
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
Click to expand...
Click to collapse
Return to stock by flashing ftf through flashtool and start from beginning.