Related
I recently updated to the most recent version of paranoid android with a clean install (full wipe) and I'm experiencing multiple bugs. There's no lock screen when I turn the screen on and the home key doesn't work at all, apart from waking the phone up (can't exit apps with it or long press for recent apps). I'm receiving no notifications in my task bar and no incoming call alerts, although the notifications and calls are working in the background. Plus the stock browser won't start up.
The strangest thing is ...after returning to stock sammy rom all these bugs are gone but when I flash cm10 or aokp based rom back, all these same bugs come back regardless of what kernel I use (latest siyah or cm10 kernel).
All system settings are unchanged from default values so these bugs aren't setting related. I've done multiple full wipes with totally clean installs but, I'm still greeted with these bugs upon booting. Does anyone have the slightest idea why I'm plagued by these issues ...the phone is pretty unusable at the moment with these problems. No home key means so many extra taps on the screen and a lot of extra time wasted and I'm missing all my calls and texts because of no notifications. Please if anyone knows how to fix this ....it'll be much appreciated!!
Bumping cause I'm kinda desperate for some help.
Has no one experienced this kind of behaviour on their GSII? I'm really at a loss as to how to fix this. I've been flashing roms on my GSII for over a year now and never heard or seen anything like this before. I really can't face going back to sammy rom which seems to be the only thing to fix this.
please list all the steps you took when you flashed CM10/paranoid
Hi and thanks for the reply. All the relevent steps I took in CWM were
1 Wiped data/Factory Reset
2 Wiped Cache
3 Wiped Dalvik Cache
4 Ran a kernel cleaning script
5 Installed PA v2.17
6 Installed gaps
7 Fixed permissions
It's just really weird how these bugs are happening on both aokp (official) and PA, so it's obviously nothing to do with the roms. Just can't figure out what the problem is at all. I'm going to try the Super Nexus rom soon to see if that's any different.
Sebalon said:
Hi and thanks for the reply. All the relevent steps I took in CWM were
1 Wiped data/Factory Reset
2 Wiped Cache
3 Wiped Dalvik Cache
4 Ran a kernel cleaning script
5 Installed PA v2.17
6 Installed gaps
7 Fixed permissions
It's just really weird how these bugs are happening on both aokp (official) and PA, so it's obviously nothing to do with the roms. Just can't figure out what the problem is at all. I'm going to try the Super Nexus rom soon to see if that's any different.
Click to expand...
Click to collapse
Can you post your present ROM and kernel details?
Jokesy said:
Can you post your present ROM and kernel details?
Click to expand...
Click to collapse
At the moment I have official aokp build 4 rom installed with Siyah v4.1.5 kernel and the very same 4 bugs persist (no lock screen, broken home key, no notifications and stock browser unable to start up)
Sebalon said:
At the moment I have official aokp build 4 rom installed with Siyah v4.1.5 kernel and the very same 4 bugs persist (no lock screen, broken home key, no notifications and stock browser unable to start up)
Click to expand...
Click to collapse
Ok.
Try these steps:
In CWM recovery,
- wipe data / factory reset
- format /system (under mounts and storage)
- flash ROM
- flash Gapps
- reboot recovery (under Advanced)
- flash ROM
- flash Gapps
- fix permissions (under Advanced)
- reboot phone
Done
Jokesy said:
Ok.
Try these steps:
In CWM recovery,
- wipe data / factory reset
- format /system (under mounts and storage)
- flash ROM
- flash Gapps
- reboot recovery (under Advanced)
- flash ROM
- flash Gapps
- fix permissions (under Advanced)
- reboot phone
Done
Click to expand...
Click to collapse
OK ..I will try your method. I'll report back as soon as I've competed thanks
Hi ...I tried the procedure exactly as you instructed but the problem persist. However ...a couple of times during the procedure I saw that cwm was having problems mounting the sdcard. "fail mounting sdcard" I think. I'm not sure whether its referring to internal or external. I don't have an external inserted at the moment anyhow. If it refers to internal sd then maybe the answer to my problem can be found there?
Sebalon said:
Hi ...I tried the procedure exactly as you instructed but the problem persist. However ...a couple of times during the procedure I saw that cwm was having problems mounting the sdcard. "fail mounting sdcard" I think. I'm not sure whether its referring to internal or external. I don't have an external inserted at the moment anyhow. If it refers to internal sd then maybe the answer to my problem can be found there?
Click to expand...
Click to collapse
SDcard refers to your external SD.
Jokesy said:
SDcard refers to your external SD.
Click to expand...
Click to collapse
Oh well then I guess it's not a problem with internal memory then. Damn I thought I was onto something! Thanks for your efforts so far but do you have any other ideas where this problem may be coming from?
Sebalon said:
Oh well then I guess it's not a problem with internal memory then. Damn I thought I was onto something! Thanks for your efforts so far but do you have any other ideas where this problem may be coming from?
Click to expand...
Click to collapse
The stock Sammy ROM you talked about, were they custom ROMs or stock unmodified firmwares?
Jokesy said:
The stock Sammy ROM you talked about, were they custom ROMs or stock unmodified firmwares?
Click to expand...
Click to collapse
The stock Sammy ROM is unmodified XX OXA from about a year ago ...I keep it around in case of boot loops during an upgrade.
Sebalon said:
The stock Sammy ROM is unmodified XX OXA from about a year ago ...I keep it around in case of boot loops during an upgrade.
Click to expand...
Click to collapse
is the stock sammy firmware Gingerbread or ICS?
Jokesy said:
is the stock sammy firmware Gingerbread or ICS?
Click to expand...
Click to collapse
Hey Jokesy, thanks for getting back to me. Its gingerbread ...that was the last time I used stock unmodified sammy. So you think if I install stock sammy ICS it may fix the problem?
Sebalon said:
Hey Jokesy, thanks for getting back to me. Its gingerbread ...that was the last time I used stock unmodified sammy. So you think if I install stock sammy ICS it may fix the problem?
Click to expand...
Click to collapse
That was the cause of the problem.
you need to first flash either Custom Stock based ICS Rom via CWM recovery, or flash an unmodified Stock firmware via Odin before flashing an Aosp ICS or Jelly bean ROM.
So please flash stock ICS firmware now.
Problem solved.
Jokesy said:
That was the cause of the problem.
you need to first flash either Custom Stock based ICS Rom via CWM recovery, or flash an unmodified Stock firmware via Odin before flashing an Aosp ICS or Jelly bean ROM.
So please flash stock ICS firmware now.
Problem solved.
Click to expand...
Click to collapse
OK will download ICS Stock rom right away ....thanks alot for your help and patience. Guys like you really make the difference in this community, I really can't thank you enough. I'll report back as soon as I'm done.
No luck thus far ...I installed NeatRomLight on which the problems weren't present but as soon as I flashed back to PA the problems were back. I tried with the same instructions you gave in the earlier post with reboot of recovery and such. This really is a strange one. What confuses me most is the fact that everything works fine with stock sammy or modded sammy but, thats the last thing I want to go back to after using aosp/cm based roms for the last 6 months.
Maybe if I download stock unmodified rom eh? Well it can't hurt to try anyways.
Were you trying to install the latest version of PA on siyah? That doesn't work. Right now PA 2.17 and above will only run on the CM10 kernel..same goes for latest pure aokp builds I think.
If you want to stick to siyah and PA, download PA 2.16. It should work.
Sent from my GT-I9100 using xda app-developers app
Hey there,
Today I received an MHL-adapter for my Galaxy S3 and wanted to try it out. Since it didn't work in combination with Slim Bean I decided to flash another rom (more on the sammy side of things). Coming across a thread with a guy pointing out a so called Chameleon crossover rom, I decided to give it a go, downloaded and flashed it. I shat bricks as I saw that, in my euphoria to try the adapter, I flashed a rom that was meant to be for the Galaxy S2!
So I restarted into recovery and tried to perform a full wipe, which didn't work, because it wasn't able to load the partitions (data etc.) then I tried to flash on a recent backup of Slim Bean, which was only partly succsessfull, meaning, that it flashed but couldn't wipe because of the reason mentioned above.
Booting into system doesn't work either, I just get a bootloop.
Right now im not quite sure, which step to take. Shall i flash on a clean stock-image via Odin or maybe try out something like One-Click UnBrick?
All your help and suggestions are highly appreciated!
rockband said:
Hey there,
Today I received an MHL-adapter for my Galaxy S3 and wanted to try it out. Since it didn't work in combination with Slim Bean I decided to flash another rom (more on the sammy side of things). Coming across a thread with a guy pointing out a so called Chameleon crossover rom, I decided to give it a go, downloaded and flashed it. I shat bricks as I saw that, in my euphoria to try the adapter, I flashed a rom that was meant to be for the Galaxy S2!
So I restarted into recovery and tried to perform a full wipe, which didn't work, because it wasn't able to load the partitions (data etc.) then I tried to flash on a recent backup of Slim Bean, which was only partly succsessfull, meaning, that it flashed but couldn't wipe because of the reason mentioned above.
Booting into system doesn't work either, I just get a bootloop.
Right now im not quite sure, which step to take. Shall i flash on a clean stock-image via Odin or maybe try out something like One-Click UnBrick?
All your help and suggestions are highly appreciated!
Click to expand...
Click to collapse
Odion stock. If that fails you'll need to find and flash with a PIT
rootSU said:
Odion stock. If that fails you'll need to find and flash with a PIT
Click to expand...
Click to collapse
Thank you so much for the quick response, I'm going to check whether it works and report back after it's done! :good:
G'Luck
Problem solved, thanks rootSU!
So, if someone is following this thread, I just want to share with you guys what I did and how it turned out:
I flashed the original firmware, according to region etc. via Odin, the procedure was succsessfull and I rebooted.
At first I had a bootloop, so I went into the stock recovery and hit "wipe /data and /cache", which was succsessfull as well, meaning that the previous problem with not being able to mount the partitions was resolved. So I went ahead and rebooted again aaand it booted!
Everything is working fine as far as i can tell, no misfunctions, hot reboots or anything similar.
Thanks very much for the quick response rootSU, which prevented me from hyperventilating .
I've rooted, unlocked bootloader and flashed stuff on my former phones (Htc Wildfire, Galaxy S) and I've never done anything like that before and nothing like that ever happened to me. So to anyone reading this, I highly encourage you not to be as dumb as me and to doublecheck what rom you're flashing and not to flash while being overly exicted about anything .
Does your adapter now work?
Sent from my GT-I9300 using xda app-developers app
Never panic. Read lots and dont do anything you don't understand. That's my advice when you're in an S3 pickle
Sent from my GT-I9300 using Tapatalk 2
Very good advice
Sent from my GT-I9300 using xda app-developers app
ok folks got a problem here and i have searched and searched and tried and tried with no luck i have an at&t unlocked note i717 i have rooted it using the method stated here http://forum.xda-developers.com/showthread.php?t=1586223 i have installed a wide vairety of custom roms as wellas recoveries the phone constently reboots i have pulled the phone apart and cleaned the power button flashed different kernels etc no matter what i do it still reboots all the time. also the battery will have a full charge and once it autoreboots the battery shows it has being dead now the phone sticks in a boot loop i am by no means new to the android game i have even built my own rom many moons ago for the SGS II but this has me stumped any help and i would be greatful
P.S. the only way it does not give me these issues is to treat it as a brick and restore to stock gingerbread
How old is the actual battery? Is it bulging at all? Might want to try a fresh battery. The battery with a full charge but is dead after reboot is a sign of bad battery.
440bro said:
How old is the actual battery? Is it bulging at all? Might want to try a fresh battery. The battery with a full charge but is dead after reboot is a sign of bad battery.
Click to expand...
Click to collapse
the battery is fine as along is it is stock but the second i stick a custom rom no matter the rom or kernel it does this i can root it and its fine but the second a custom rom is introduced i have the problems
The_Fallen_angel said:
the battery is fine as along is it is stock but the second i stick a custom rom no matter the rom or kernel it does this i can root it and its fine but the second a custom rom is introduced i have the problems
Click to expand...
Click to collapse
Sounds like you have done your reading, but I have to ask, how clean are you?
Personally, I wipe 3 times
Flash rom 2 times
Gapps 1 time
Wipe davlik and cache
Wait 10
Reboot again and do your thing
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Datz pretty clean....i dk the same expect I don't always flash ROM twice.:beer:
*S.O.F.A*2SHAYNEZ*K.C.C.O*
shayneflashindaily said:
Datz pretty clean....i dk the same expect I don't always flash ROM twice.:beer:
*S.O.F.A*2SHAYNEZ*K.C.C.O*
Click to expand...
Click to collapse
How think do you drunk I am Shayne? :beer::beer::beer: Dayup!!
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Sounds like you have done your reading, but I have to ask, how clean are you?
Personally, I wipe 3 times
Flash rom 2 times
Gapps 1 time
Wipe davlik and cache
Wait 10
Reboot again and do your thing
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
That is a given i have learned from past experience that wiping just once sometimes just is not good enough. strangely enough i returned the phone to stock unrooted. from there i install hybrid rom and did not have any issues the battery said it was a full charge the phone stayed on did not reboot untill today this afternoon i went and logged into facebook and the second it logged in bang there was the reboot. before that i made calls and went tot he play store etc etc with no hiccups this is really got me stumped
Wiping data and cache is not always good enough. You should also format your system partition. If not you will have system files from the previous ROM on your phone even though you do a full wipe.
Your issue may be with the way you are rooting your phone. Install your factory ROM using odin. Then use odin to flash CWM or TWRP recovery. Then flash a superuser version using recovery. The tutorial you spoke of mentioned kernels and you may be flashing a kernel for gingerbread on a JB ROM. This would definitely mess your phone up. Stay away from the kernels mentioned in this thread as the info is ANCIENT. After rooting (actually you don't even need to install superuser to flash a custom ROM) install your custom ROM. And only flash kernels recommended for that particular ROM.
Agoatamers words are always solid. I myself dont like to flash alternate kernals as they often seem to invite more maintainence. If it doesnt work with kernal built with, then I dont use.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Agoattamer said:
Wiping data and cache is not always good enough. You should also format your system partition. If not you will have system files from the previous ROM on your phone even though you do a full wipe.
Your issue may be with the way you are rooting your phone. Install your factory ROM using odin. Then use odin to flash CWM or TWRP recovery. Then flash a superuser version using recovery. The tutorial you spoke of mentioned kernels and you may be flashing a kernel for gingerbread on a JB ROM. This would definitely mess your phone up. Stay away from the kernels mentioned in this thread as the info is ANCIENT. After rooting (actually you don't even need to install superuser to flash a custom ROM) install your custom ROM. And only flash kernels recommended for that particular ROM.
Click to expand...
Click to collapse
I have been in this game for a while now and i have flashed more androids than i can count this phone is not the first note that I have flashed but it is the only one that i have seen this issue with as far as flashing kernels i did not use the kernels in that post untill i had returned to stock with GB then i used them the way you mentioned above is the way this phones was flashed several times I have tried many different roms without flashing kernels and then as last result tried a few defferent kernels as well to see if the kernel was an issue as i have had issues with kernels in the past on the SGS2 doing this with crappy kernels, although they were an easy fix flashing siyah pretty much fixed that issue. here is an update on the phone situation. i have been running hbrid rom for almost 24 hours with no reboot (fingers crossed, knock on wood ) the only thing i have done different I did switch batteries due to being out and my primary batt died and used my back up so i do believe it very well may have been the battery, the battery is not bulging as of yet but that does not mean anything as the battery could still be bad so we will see again fingers crossed i will kep this updated for at least 48 hours as long as there is no more problems i will mark this as solved via the battery replacement
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
maybe try this
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Joshua Mr PC Repair said:
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Click to expand...
Click to collapse
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
I just Tried it again .
Had No Issues ,
Can You Try with a new SD Card .
Then Do The Wipe
also load TWRP Via Recovery , If You have CWM Go to Install Click > TWRP .
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Put on SD Card and install
captemo said:
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
This is the one that works for KK
[TWRP_Recovery_2.7.0.0][Unofficial][quincyatt]
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices. So please provide a detailed step-by-step information if you can.
SockmanTGR said:
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices.
Click to expand...
Click to collapse
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
25625292 7345
captemo said:
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
Click to expand...
Click to collapse
I followed your instruction with the kernel(http://forum.xda-developers.com/showthread.php?t=2326786) Had to download it directly to my phone. It didn't like it from my laptop.
Successfully installed.
I'll let you guys know if my problem continues,
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
You are not using twrp from the thread linked. Also do NOT use the twrp app for the recovery as my recovery is not found there. It can only be found in my thread. Flash it in recovery & you're good to go.
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
i had the same problem and went to liquid smooth and is stable
jemsTV said:
i had the same problem and went to liquid smooth and is stable
Click to expand...
Click to collapse
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
SockmanTGR said:
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
Click to expand...
Click to collapse
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
delawaredrew said:
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
Click to expand...
Click to collapse
Would I need to reflash the ROM to ally another kernel?
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
As instructed, you need to do some reading. In my last post I gave you instructions on how to add kernel.
Help yourself first, then others will be more than happy to assist.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
I'll give you some slack 'cause I am still close enough to my first flash that I remember being full of questions, but at least read the OP and most recent pages in your ROM thread. You should skim through it all ideally but some are 100+ pages so....
Kernel switching in general does not require any ROM action, there are likely cases that it might be useful but I've never had a problem. You will need to ensure that the kernel is matched to your ROM; KitKat or Jellybean or whatever. I usually do it as I flash a ROM but I have gone back and installed a kernel on a running ROM plenty of times; Uber for instance was released after I had BeanStalk up and running, it is a good kernel so I switched to that.
As a more general point the Note is hard to brick, as long as you don't somehow mess up the recovery (CWM or TWRP) you are just a quick restore away from back to normal. Use the backup function in your recovery, it is your friend and savior. Keep a copy of the back-up on your PC (or Mac) and you will usually be golden.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
If you are on BS Rom you should know that all you need to to know is on the OP post-the rom and the patch. The latter contains about 5 different kernels which you can switch betw. to your hearts content. The patch is n00bie proof to make your switches. Really hit BS OP.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
Just like all the other kind gents adv'd, it's all in patch's OP:
http://forum.xda-developers.com/showthread.php?t=2535857
Including polluti0n's patches thread:
http://forum.xda-developers.com/showpost.php?p=50529734&postcount=854
He uses aroma installer, so when you flash it (personally, I did it with CWM) you don't need to wipe cache/dalvik nor wipe phone, he mentons this on patch's thread while answering questions I believe. The screenshots show you some differences between the kernels he has available, either CM, Uber or PAC.
Personally, I'm using PAC since for me it seemed to work better with the Xposed's Netflix workaround, whereas it didn't work that well with Uber.
Also, the patch provides fixes, for camera, screen flicker and such.. Give it a try, and you'll definitely love your phone more!
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Snake2k said:
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Click to expand...
Click to collapse
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
es0tericcha0s said:
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Click to expand...
Click to collapse
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
ikuni123 said:
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Snake2k said:
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634408
According to that, only 13 is supported. I dunno if the that thread hasn't been updated or whatever, but something to consider.