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.
Related
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
berdo said:
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
Click to expand...
Click to collapse
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
btw there is a Q&A section.
bigjoe2675 said:
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
Click to expand...
Click to collapse
I apologize if I did not make this clear but I have Rom Manager installed and CWM was updated to the latest version. I would reboot into CWM, do a factory reset, wipe cache, dalvik caceh, install rom and reboot. It would just sit at the samsung screen. I did not go into mounts and storage and do that but I will now. The process I use on my AT&T note is the same process I used on my Rogers note and I am able to install any ROM i want on my rogers note.
I have flashed roms probably over 100 times since my samsung captivate. I just didn't know if the note had another step involved. Like S-Off on HTC phones for example.
I have been using the standard version of cwm but I am trying the touch version now. Will update.
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
did you check if bootloader is unlocked?
berdo said:
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
Click to expand...
Click to collapse
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
animatechnica said:
did you check if bootloader is unlocked?
Click to expand...
Click to collapse
elry567 said:
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Animatechnica - It is my understanding that the bootloader is not locked on the Galaxy Note. I have not seen anything about unlocking the bootloader in any thread on the i717.
elry567 - do not have busy box installed - never saw anything requiring it to be installed. I will try that as well.
Well this time I got a status 7 error in CWM which can be a lot of different things. I am up to date on CWM, the rom I know works for the galaxy note (I am running it on my other one AND I have seen video of it working on an AT&T branded Note) so I don't know. I did a google search on the error and everything I found does not seem to apply. It is really starting to piss me off. Any help is appreciated.
Here is the video, sorry about my cam skills but you get the gist. I took this video with a i717r that is running the rom I want to install on the phone in the video.
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
rangercaptain said:
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
Click to expand...
Click to collapse
Done both, doesn't seem to make a difference. I will definitely use the button method from here on out though.
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
+1
berdo said:
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Click to expand...
Click to collapse
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
bigjoe2675 said:
+1
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
Click to expand...
Click to collapse
Done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
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
Suddenly I cannot flash ROMs. I've downloaded, and have tried to flash, 2 ROMs. They are downloaded correctly, too. I've downloaded them multiple times as well.
When I try to flash, it gives me a bunch of prop errors and then gives me an error that the ROM cannot be flashed. I am able to restore backups, though.
I'm not sure what's causing this, as it happened out of the blue. A few days ago I flashed a ROM fine but reverted back to my original ROM because I did not like the other ROM.
I always wipe data and wipe system, and have even wiped cache. Really I'm at a loss her so any help would be greatly appreciated.
what two roms are you trying to flash and on what recovery/version?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
BoostedB18C said:
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
Unfortunately I got the same error, albeit it seemed to move along a little more than before. The exact error is as follows:
"file_getprop: failed to stat /sdcard/kernal.pro. Error flashing zip (and a few other irrelevant things)"
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Milimbar said:
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Click to expand...
Click to collapse
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
BoostinBen said:
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
Click to expand...
Click to collapse
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
BoostinBen said:
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
Click to expand...
Click to collapse
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
BoostedB18C said:
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
Click to expand...
Click to collapse
Thanks. I'll give this a try and report back.
Sent from my SCH-I605 using Tapatalk 2
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
BoostinBen said:
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
Click to expand...
Click to collapse
Any ideas why zip installs give me a kernal.prop error?
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
Have you tried just flashing a new kernel? there was some issues with a few versions of sabre kernel.... get the newest one or Perseus or something else.
Install the newest version of your recovery (CWM or TWRP)
Boot into recovery.
Clear dalvik/cache
Flash your kernel
Clear dalvik and cache again (just because thats what i do, no idea if its needed)
Test your installed ROM or just install a new ROM following the instructions in the OP of the ROM thread...
If there is no install instructions, I always:
Make a nandroid backup!
Clear dalvik/cache
Factory reset (wipe all but SD card, depending on your recovery)
Install ROM
Clear dalvik and cache again
Install GAPPS (Google Apps package) if not included in ROM
Reboot system
Profit?
Good Luck, report success/failure
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
michigan66 said:
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'm using Saber's overclocked one. I will grab another kernal and give it a shot and report back.
Got this fixed by switching to another kernel.
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!
Hi,
I am using archidroid from a while now.
And tried to install both ressoraction remix and cm12 alpha,
Both attempts Ended with boot loops.
After I flashed arter97 kernel I got it booting but no keyboard and status Bar.
Any ideas? Thanks, Ido.
ido100 said:
Hi,
I am using archidroid from a while now.
And tried to install both ressoraction remix and cm12 alpha,
Both attempts Ended with boot loops.
After I flashed arter97 kernel I got it booting but no keyboard and status Bar.
Any ideas? Thanks, Ido.
Click to expand...
Click to collapse
Don't forget cm12 is alpha so you will find some bugsSaying that you need to do a full wipe before flashing (not a factory reset) you need to format system, data, cache,dalvik cache etc you can use this zip >> http://forum.xda-developers.com/galaxy-s3/general/tool-mega-wipesuper-wipefactory-t1832326 << use the mega wipe zip and make sure you have your rom on ext sd card ready to flash after wiping.Make sure to read the thread thoroughly and understand what it does.
Also make sure after flashing to factory reset if you get a bootloop.
Tried all of the above.. Actually tried anything but Flash stock using odin and re root.
I know the Development is in alpha stage but I'm pretty sure status bar should work..
Any ways of getting stuff working without using odin?
Thanks!
Sent from my GT-I9300 using Tapatalk
ido100 said:
Tried all of the above.. Actually tried anything but Flash stock using odin and re root.
I know the Development is in alpha stage but I'm pretty sure status bar should work..
Any ways of getting stuff working without using odin?
Thanks!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Yep sorry i meant it as bugs that may cause bootloops not the status bar that would be a big bug lol.Well if you have done a full mega wipe then it must be the rom that's causing the problem so either download again (bet you done that lol) or ask in thread (one more post and you can ask in the thread) but i don't think returning to stock will solve this particular issue (especially since you have done a megawipe).