Related
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Fixed it by odin
Sent from my SCH-I545 using Tapatalk 2
oneandroidnut said:
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
rickt1152 said:
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
Click to expand...
Click to collapse
I don't think there is another way. I flashed numerous roms in hope of something that would work and no. Phone also ran hot like over 100°+ at idle or screen off and lagged bad when I did get it to boot. After flashing back to stock rerooting and restoring my backup it runs like brand new. Wonder is rls 7 is screwing with something?
Play it safe and go back to stock man
Sent from my SCH-I545 using Tapatalk 2
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
TheAxman said:
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
Click to expand...
Click to collapse
Doesn't apply to us or rom wouldn't have booted first time after install. And a quick wipe of cache boots it so can't be that issue thanks though
Sent from my SCH-I545 using Tapatalk 2
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
TheAxman said:
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
Click to expand...
Click to collapse
Then why would wipe cache make it work? & no issues before with it. Had to be a mod we tried to install
Sent from my SCH-I545 using Tapatalk 2
This is the pre-alpha thread of OmniROM for the Samsung Galaxy Note 2 (i605). More information can be found here.
This build is very bare bones at the moment. Don't let flashing this now turn you down from trying it again in the future, a lot of changes are coming soon. I would still consider this much more of a tester than a daily driver unless bare bones is your style. The rom is very smooth and fast though probably for that very same reason.
Source:
https://github.com/omnirom
https://gerrit.omnirom.org/#/q/status:open,n,z
https://github.com/omnirom-slickrick
What doesn't work:
You tell me!
Installation method:
Wipe all if coming from another rom
Flash OmniROM
Flash GApps
Reboot
This rom does not come with root by default. Flash SuperSU in recovery if you want root!
Flash at your own risk! No one else is responsible if your device bursts into flames
To try out multiwindow, go to recents and long press an app. Click add to split view and repeat to add another app. Keep in mind its still buggy at the moment
Have fun and enjoy!
For "pre-alpha" this is a very solid stripped to the basics AOSP ROM. Obviously features like customizing and themes will get added in but for now this is pretty good. Basic stuff like wifi, bluetooth, phone, etc are working on my end here. Looking forward to seeing where this ROM goes. Will be keeping my eyes on this.
Excited to see this come together.
Sent from my SCH-I605 using xda app-developers app
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
dagod80 said:
Wish I could get this working on T-Mobile. Zip fails in recovery. Any ideas? TIA
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Boo so excited for 4.3... my socks are wet
ssmr2t said:
I tried messing with the updater script to match that of a tmobile note2, but didnt work
I really want to try this :crying:
Click to expand...
Click to collapse
There's a working art version on RootzWiki
Sent from my GT-N7105 using xda app-developers app
im definitely excited about seeing this rom come rogether in the future! thanks Rick!
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Pilatus47 said:
Try to flash the last Rom with the working baseband. And then flash Omni.
Saludos
Click to expand...
Click to collapse
Dirty flash on top of an existing rom with working data? I will try over CM 10.2 to see if that works.
Update: That was a no go. Stuck at boot...
R-Rizzo said:
Are you flashing any LTE fix zip?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I am afraid I have not seen that zip. Is it the one found here?
Update: Tried this and the apns-conf.xml from slick_rick found here just to see if it would resolve the issue but still a no go...
Click to expand...
Click to collapse
PapaJohnMc said:
I am not able to get data on this rom.
I have Baseband version Unknown.
As mentioned here, I made sure I am using the latest TWRP... Any ideas?
Taken from here...
Click to expand...
Click to collapse
yeah i couldn't get data to show up, but I'm okay with that the rom was definitely smooth and I'll have to try it out again soon. thank you Rick! you kick ass like always
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here is what I have. I haven't done a logcat in quite some time. Hope this helps!
Thanks
This is my daily driver so I am flashing back to CM 10.2 for now... Gotta be accessible.
slick_rick said:
That's weird that data isn't working. If you can grab a logcat please.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'll have to restore my nan and run a log.
EDIT: here's my logcat @slickrick
EDITdos: if that's not enough I'll run another logcat just let me know!
Any progress on the data issue? I tried again and still a no-go on data.
Thanks!
sorry to bring up a semi old thread, but i wonder if because i flashed omni using twrp 2.6.3.0 that's why i didn't have data... ima try with cwm and see if i have data then
EDIT: yup that didn't fix my radio issues..
Data working
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Bluetooth
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
I wiped cache and dalvik rebooted and reconnected bluetooth and everything is good.
dturneys said:
When I did a normal flash with or without gapps no data & SU and "unknown baseband". Flash rom then gapp, then SU let boot, then boot back into TWRP & make a backup in TWRP only of "system" and "data". Flash CM 10.2 nightly & gapps allow data to lock and also open maps and allow GPS to lock. Reboot back into TWRP & restore the previous Omni / gapps / SU backup. Wipe dalvik & cache, reboot and everything should be good to go.
The rom has been very stable with no reboots & multi window works well.
The only issue I have experienced is a buzzing sound on call bluetooth on callers side until complete connection occurs.
Looking Good!
sent from Note 2 i605 running Omnirom pre-alpha with data.
Click to expand...
Click to collapse
This worked for me! Thanks!
Sorry
Sorry, I am going to be "that guy" who proves my ignorance. I would love having the OMNI rom on my i605, but I couldn't get data or voice working. I saw the whole thing about backing up and restoring but I could not get that to work either. Are you working on a 4.3 or 4.4 release?
Thanks
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
sansari123 said:
I am trying to flash a Sprint Samsung Note 3 with Cyanogenmod 11. I downloaded the imaged, checked the hash, and put it on the external sdcard. When I use TWRD to flash it, after wiping / factory default, I get the following message : Unable to mount '/usbstorage along with a Success message from TWRD. But when I reboot the phone it gets caught in a recovery loop. I have tried older releases of Cyanogenmod 11 also. Is there something I am missing? I looked online, and found some comments about wiping the data before flashing. But I had done that.
Click to expand...
Click to collapse
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
You flash gapps too ? And wipe data and system before flashing . The unable to mount error means nothing
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I found this link about the error. http://forum.xda-developers.com/showthread.php?t=2507403 but the link to the script provided to fix this issue does not work. I have made a comment about it. Hope they can fix it.
Just to double check, I am putting my zip files for Cyanogenmod and Gapps on the sdcard. That is what we are supposed to do right?
sansari123 said:
Yes I did. For some reason it keeps getting stuck in boot loop. So you are saying I should look into something else? The unable to mount message does not mean much?
Click to expand...
Click to collapse
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
topherk said:
Epix,
I'm not familiar with AOSP Roms on the Note 3, but I know that people were having major issues when upgrading from JellyBean to KitKat TW Roms. They had to Odin flash the stock NAB update first, then they were able to flash NAB (KitKat) Roms. Is this the same procedure for AOSP KitKat Roms?
I haven't seen anything on the various AOSP threads about having to be on NAB or newer (i.e. KitKat) in order to flash their Roms.
Click to expand...
Click to collapse
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
It did not matter what bootloader you were on when flashing aosp roms .... as they were not built to need that .... you could have mj4 and flash 4.4.2 aosp roms just fine ... most times it is not wiping system as touch wiz was on system and it needs wiped to install aosp ....I personally wipe all but external and flash from there .... I hit advanced wipe and wipe data cache davlik system and internal. .. but that is just me
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Ah, that's good to know. I wasn't sure if AOSP Roms needed the updated bootloader.
I also do a full wipe in TWRP before flashing a new Rom. I find it prevents a lot of the various issues I've seen with dirty flashers on here.
Thanks for the input!
Epix4G said:
When going from stock to any aosp always wipe system that is what most do wrong
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yea I did a complete wipe of everything. Still got the error. I am now trying another microsd.
Here is the SM-T237P Stock Rooted Deodexed 5.1.1 BOH7 Base Knox Free Rom.
Features
Rooted
Deodexed
SD Card Write Fix
Updating from kitkat still has some bugs so I have pulled the files for now
Directions If Coming From KitKat
Odin Method To Update Firmware
Place rom on sd card
If comming from KitKat flash the firmware SM_T237P_BOH7_FIRMWARE_ONLY.tar.md5 using Odin Uncheck The auto reboot under options in Odin
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Recovery Method
Place Rom On SD or Internal Storage
Place SM_T237P_BOH7_Firmware.zip On SD or Internal Storage
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Install SM_T237P_BOH7_Firmware.zip Do Not Reboot
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Directions If Coming Lollipop Rom
Place rom on sd card
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
It May Take Up To 10 Min Too Boot!
Enjoy!
Downloads
SM_T237P_BOH7_ROOTED_STOCK_DEODEXED.zip
Mini Firmware Update Files
SM_T237P_BOH7_FIRMWARE_ONLY.tar.md5 (Includes Custom Recovery by @moonbutt74)
KitKat Roms
Here is the SM-T237P Stock Rooted Deodexed 4.4.2 NL1 Base Knox Free Rom. Must have Custom Recovery Installed.
Feel Free To Use As A Base If Anyone Wants Too!
Custom Recovery Found Here
Or You Can Use Odin and Flash NL1 Firmware Only Including Bootloaders, Modem, Kernel, and Custom Recovery(By @moonbutt74).
Directions
Place rom on sd card
If on Older Firmware Flash The NL1 Firmware With Custom Recovery Already included Using Odin
Reboot to recovery(Hold Power,Volume UP And Home Button at same time)
Choose Wipe To Install New Rom
Or Manually
Wipe System
Wipe Cache
Wipe Data
Install Rom
Enjoy!
Downloads
SPR_T237_STOCK_NL1_DEODEXED.zip
Mini Firmware Update Files
SM_T237P_NL1_FIRMWARE_ONLY.tar.md5 (Includes Custom Recovery by @moonbutt74)
SM_T237P_NL1_KERNEL_ONLY.tar.md5
Mods/Updates
Coming Soon!
Thanks for making a deodexed version.
I have had this awhile I just forgot to post it.
Downloaded...
Will install and check it out as soon as I get time.
Thanks !
will this work on the SM-T230?
jdmsohc22 said:
will this work on the SM-T230?
Click to expand...
Click to collapse
No
Anybody getting the notification bar not working in fact it doesn't matter what app is open but the top won't work for a bit then it'll work again?
It did it on straight up stock with root. I've redone the recovery and flashed this ROM and its happenening again. It took a while to do it like a few hours or so. Any thoughts?
Smirky Guitars said:
Anybody getting the notification bar not working in fact it doesn't matter what app is open but the top won't work for a bit then it'll work again?
It did it on straight up stock with root. I've redone the recovery and flashed this ROM and its happenening again. It took a while to do it like a few hours or so. Any thoughts?
Click to expand...
Click to collapse
I don't think I've had any issues with the notification bar not working while using this build. But I'll double check when I get out of work for you.
VerneVerne said:
I don't think I've had any issues with the notification bar not working while using this build. But I'll double check when I get out of work for you.
Click to expand...
Click to collapse
Its not just notification bar, its anything at the top like settings buttons or tabs. It literally just did it again for 10 mins after booting from being off. Its working normal again. Weird.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Smirky Guitars said:
Its not just notification bar, its anything at the top like settings buttons or tabs. It literally just did it again for 10 mins after booting from being off. Its working normal again. Weird.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I just got home and asked the wife if our tablet had been acting up lately and her response was no. I did have a slight issue with my brightness and volume slider bars disappearing but that was the original stock rom. That was fixed by reflashing using Odin.
I assume you tried a factory reset and all the other standard fixes?
Sorry I can't help you more. Good luck
Are you familiar with kernel development? I see there are custom kernels for other galaxy tab models and even other SM-T23X models but nothing for the sprint variant. Or would anyone have any resources for me to possibly learn how to build my own ? thanks
work great in my tab, thanks for share mate!!
hi
hi is the French language???
Uploaded New 5.1.1 Lollipop Rom
jrkruse said:
Uploaded New 5.1.1 Lollipop Rom
Click to expand...
Click to collapse
Super! I will check it out ASAP
I thought about learning this and creating one myself but haven't had time.
Thank you very much!
Rick
PS - I had recently gone back to factory defaults since it had been so long since last rom I felt i needed security updates.
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
jrkruse said:
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
Click to expand...
Click to collapse
Well, I downloaded it but haven't been able to get it installed just yet. Maybe sometime tomorrow if all goes well. Thank you
jrkruse said:
I can't believe not one person has posted and said if the rom worked or not. Its been downloaded 50 times so I assume it must work.
Click to expand...
Click to collapse
Did you create a custom kernel? What method of root are you using (system-less, or full system root)? @moonbutt74 is working a custom kernel for the t237p, but not really sure how long it'll take...
fiddy619 said:
Did you create a custom kernel? What method of root are you using (system-less, or full system root)? @moonbutt74 is working a custom kernel for the t237p, but not really sure how long it'll take...
Click to expand...
Click to collapse
This is a systemless root method, so if you factory reset you will loose root and have to reflash the beta 2.66 root zip. The kernel source has not been released yet for our device so until we have that there will be know custom kernel.