[Kernel/Recovery][P75XX] A1 Kernel V1.9/TWRP2.6.3.0

Stuck After 1.3 on Samsung Screen?

  • No, and hope I never do.

    Votes: 179 82.9%
  • Yes, but I solved it by reflashing

    Votes: 8 3.7%
  • Yes, but I solved it by flashing V1.3 or older

    Votes: 8 3.7%
  • Yes, and had to reflash full stock

    Votes: 21 9.7%

  • Total voters
    216
Search This thread

Gethsemane

New member
Feb 20, 2016
3
0
After reading many threads, watching many youtube videos, much screaming and pointing fingers and shouting why! why? why am i finding this so difficult? what am i obviously not seeing? I come to you a broken man :(

I've an old but much loved Samsung galaxy tab 10.1 GT-P7510, a couple days ago and after much reading i decided to take the plunge and try to breath new life into this aging bit of technology. So Ive managed to root it, installed TWRP 2.2.0 ! installed super user (updated that via the playstore to superSU V2.46) and then install CyanogenMod 10.1-20140216-NIGHTLY-p4wifi and then gapps-jb-20130129-P75xx.zip

As it stands my GT- P7510 is
andriod version 4.2.2
kernel 3.1.10-cyanogenmod+build01
recovery TWRP 2.2.0


Now id like to install the Twrp2630-wifi zip found in this thread but for the life of me i don't understand how i update TWRP? every video i see talks about using goo manager but that's no longer available? and its alternatives don't recognize my device or version of TWRP. After two days and many, many hours i admit defeat, if some caring soul would please enlighten me, id be most appreciative.

Thanks in advance and apologies if theres a more suitable thread to ask this question
 
Last edited:

rtiangha

Senior Member
Jan 3, 2012
231
76
After reading many threads, watching many youtube videos, much screaming and pointing fingers and shouting why! why? why am i finding this so difficult? what am i obviously not seeing? I come to you a broken man :(

I've an old but much loved Samsung galaxy tab 10.1 GT-P7510, a couple days ago and after much reading i decided to take the plunge and try to breath new life into this aging bit of technology. So Ive managed to root it, installed TWRP 2.2.0 ! installed super user (updated that via the playstore to superSU V2.46) and then install CyanogenMod 10.1-20140216-NIGHTLY-p4wifi and then gapps-jb-20130129-P75xx.zip

As it stands my GT- P7510 is
andriod version 4.2.2
kernel 3.1.10-cyanogenmod+build01
recovery TWRP 2.2.0


Now id like to install the Twrp2630-wifi zip found in this thread but for the life of me i don't understand how i update TWRP? every video i see talks about using goo manager but that's no longer available? and its alternatives don't recognize my device or version of TWRP. After two days and many, many hours i admit defeat, if some caring soul would please enlighten me, id be most appreciative.

Thanks in advance and apologies if theres a more suitable thread to ask this question
Boot to recovery and flash the new TWRP zip (like you would any other ROM), and then reboot to recovery again in order to load the new version of TWRP.

Although if you're going to restart everything from scratch, you might as well install one of decatf's Lollipop or Marshmallow Roms (he's even ported TWRP 3.0.0.0 to our devices, and his Roms include F2FS support).

Sent from my GT-N5110 using Tapatalk
 
Last edited:
  • Like
Reactions: Gethsemane

Gethsemane

New member
Feb 20, 2016
3
0
Boot to recovery and flash the new TWRP zip (like you would any other ROM), and then reboot to recovery again in order to load the new version of TWRP.

Although if you're going to restart everything from scratch, you might as well install one of decatf's Lollipop or Marshmallow Roms (he's even ported TWRP 3.0.0.0 to our devices, and his Roms include F2FS support).

Sent from my GT-N5110 using Tapatalk

Thank-you for your swift reply rtiangha. Id thought as much but wasn't entirely sure, thus my post. A quick question or two, firstly, I'm guessing there's no need to perform a wipe before upgrading TWRP (unlike when installing a rom)? and will i see further improvements with one of your above mentioned roms over CyanogenMod Ive installed? (that may sound daft, but bare with me, I'm on a learning curve)

once again, thankyou.
 

rtiangha

Senior Member
Jan 3, 2012
231
76
Thank-you for your swift reply rtiangha. Id thought as much but wasn't entirely sure, thus my post. A quick question or two, firstly, I'm guessing there's no need to perform a wipe before upgrading TWRP (unlike when installing a rom)? and will i see further improvements with one of your above mentioned roms over CyanogenMod Ive installed? (that may sound daft, but bare with me, I'm on a learning curve)

once again, thankyou.
No need to wipe if you're just upgrading TWRP, but you may have to perform a factory reset and perhaps wipe /system if installing one of decatf Roms.

As for improvements, it depends on your definition of it. decatf's Roms are current, which means they have all of Google's latest security patches installed, whereas that CM version you're using is still vulnerable to various security exploits that have never been patched because the ROM has been unmaintained for years.

On the other hand, that version of CM may run faster because the hardware is old and the various proprietary hardware drivers were never updated by Nvidia. However, decatf put in a lot of work in writing wrappers and compatibility layers that allow the newer Roms to interface with the old drivers so his Roms are the best ones to use if you're looking for Lollipop or Marshmallow Roms to try. Still not as fast as running them natively, but faster than running them in software.

His Lollipop ROM runs faster than his Marshmallow one, but while he just updated the Lollipop one, he may no longer do so as he's concentrating on Marshmallow development. So the Marshmallow ROM has a higher likelihood of being maintained over a longer period of time. I've switched over to Marshmallow, but if he were to commit to compiling new Lollipop Roms every time Google issues their monthly Lollipop security patches, I would have probably stuck with Lollipop (still might, since Marshmallow still has a few quirks).

That said, if you're a Gapps user, over time, many Google Apps are becoming incompatible with our device because of its lack of NEON instruction set support. So if you're wondering why certain apps no longer work after updating them, that could be why. So one side benefit of going with the older CM ROM is that there's a higher likelihood that your favourite apps will work with it, because they won't update to newer versions that no longer support JellyBean (althogh that still doesn't guarantee that those apps won't require NEON support, so make sure to back up your favourite apps before upgrading them in case they stop working). But again, if you go that route, you risk leaving yourself open to various unpatched security exploits.

So there are different pros and cons depending on how you want to proceed.

Sent from my GT-N5110 using Tapatalk

---------- Post added at 09:45 AM ---------- Previous post was at 09:29 AM ----------

Also, if you want to test the various different Roms, decatf also ported over Multirom support to our device (just look for his thread) which allows you to dual or triple boot different Roms. So you could install all three (CM, 5.1 & 6.0) and see which one works best for you before settling on one.

So, lots of options).

Sent from my GT-N5110 using Tapatalk
 

Gethsemane

New member
Feb 20, 2016
3
0
No need to wipe if you're just upgrading TWRP, but you may have to perform a factory reset and perhaps wipe /system if installing one of decatf Roms.

As for improvements, it depends on your definition of it. decatf's Roms are current, which means they have all of Google's latest security patches installed, whereas that CM version you're using is still vulnerable to various security exploits that have never been patched because the ROM has been unmaintained for years.

On the other hand, that version of CM may run faster because the hardware is old and the various proprietary hardware drivers were never updated by Nvidia. However, decatf put in a lot of work in writing wrappers and compatibility layers that allow the newer Roms to interface with the old drivers so his Roms are the best ones to use if you're looking for Lollipop or Marshmallow Roms to try. Still not as fast as running them natively, but faster than running them in software.

His Lollipop ROM runs faster than his Marshmallow one, but while he just updated the Lollipop one, he may no longer do so as he's concentrating on Marshmallow development. So the Marshmallow ROM has a higher likelihood of being maintained over a longer period of time. I've switched over to Marshmallow, but if he were to commit to compiling new Lollipop Roms every time Google issues their monthly Lollipop security patches, I would have probably stuck with Lollipop (still might, since Marshmallow still has a few quirks).

That said, if you're a Gapps user, over time, many Google Apps are becoming incompatible with our device because of its lack of NEON instruction set support. So if you're wondering why certain apps no longer work after updating them, that could be why. So one side benefit of going with the older CM ROM is that there's a higher likelihood that your favourite apps will work with it, because they won't update to newer versions that no longer support JellyBean (althogh that still doesn't guarantee that those apps won't require NEON support, so make sure to back up your favourite apps before upgrading them in case they stop working). But again, if you go that route, you risk leaving yourself open to various unpatched security exploits.

So there are different pros and cons depending on how you want to proceed.

Sent from my GT-N5110 using Tapatalk

---------- Post added at 09:45 AM ---------- Previous post was at 09:29 AM ----------

Also, if you want to test the various different Roms, decatf also ported over Multirom support to our device (just look for his thread) which allows you to dual or triple boot different Roms. So you could install all three (CM, 5.1 & 6.0) and see which one works best for you before settling on one.

So, lots of options).

Sent from my GT-N5110 using Tapatalk

Once again thankyou rtiangha, for your quick, clear and concise reply. You've helped me a great deal. cheers.
 

ofthecentury

New member
Jan 31, 2012
1
0
Is there a tool to unpack and repack boot to be able to edit ramdisk? I've done my own for other devices or did it manually but just wonder if someone here shared it online or knows any existing tool for our Galaxy Tab 10.1? Thanks a lot camelot
 

Top Liked Posts

  • There are no posts matching your filters.
  • 187
    :good: First of all :good: Thank you for your patronage!!! :D:cowboy::laugh::victory:

    Before you do anything: This is purely at your own risk and I will not be responsible for anything that happens to your tablet. I flashed it on mine at my own risk.

    Compatibility Information: There are 2 different versions. 1 for stock and 1 for Cyanogenmod. Even though the kernels are intended for the 3G tablet it will work just fine on a WiFi only tablet (like mine). This makes the build process less messy.

    **Sources Fully documented v1.9 beginner friendly sources now available including the build script. If more explanations are required, please say so. However, remember that the explanations are not intended to be a blind step by step instructions of going from samsung source to A1.

    TWRP V2.6.0.0: Please read: do not worry about any kind of "E:A: Render Error". This is a side effect of removing some image files to save place on the recovery image so it will fit on the 5MB. The error simply means it failed to show (render) and image file that it is looking for. This is not harmful at all. If you can't flash the recovery please try the dd method.

    TWRP V2.6.3.0: There are no more E:A Render errors. All graphics that were removed are there. Also, the recovery will install supersu if no root is detected. That feature has also been restored. The kernel has been stripped of anything not recovery related to shrink it down. It also has selinux support which allows the "set_metadata" zip installation to work. The download is in the attachments below.

    Changelog:
    Changelog:
    • Voodoo sound <-- new to version 1.0
    • USB charging enabled as well as charging from other chargers *** fixed V1.5.4 thanks to pershoot
    • Overclock to 1.2GHz <-- new to version 1.2
    • NTFS modules enabled, ondemand default frequency scaler, noop default disk io scheduler <-- new to version 1.2.1
    • GPU overclock from 333MHz to 400MHz. <-- new to version 1.3
    • Overclock to 1.4GHz <--new to version 1.4
    • Support for Current Widget <-- new to version 1.5
    • CIFS enabled in kernel config, 1.4GHz attempted stability fix (thanks to jaswinky) <--new to version 1.5.2
    • Wifi driver compiled as module <--new to V1.5.3
    • More voltage anomalies fixed, updated battery driver to pershoot's 3.1 <-- new to V1.5.4 and V1.5.5XE
    • Fixed charging boot bug <--new to V1.5.6SE
    • (In case you were wondering 1.5.7 had an issue in it.)
    • Disabled frequency lock, added 1GHz default max (you can change it to 1.2GHz or 1.4GHz after boot), 216MHz default min CazeW's suggestion <--new to 1.5.8SE+XE
    • Enabled pershoot build/vfp optimization commit, added 150MHz minimum frequency <-- new to 1.5.9SE+XE
    • Boot script support (put yours as /data/local/a1init.sh) <-- new to V2.0
    • Smarter ram disk that only initializes 3G on 3G tablets<-- new to V2.1
    • 1.5GHz && 1.6GHz OC available, cifs utf8 kernel module available <-- new to V2.2
    • Support for CM9 <-- new to V2.2CM
    • Enabled xbox controller module as xpad.ko <--new to V2.2.1
    • NTFS moved to kernel module instead of built in, CIFS moved to kernel module instead of built in, enabled option.ko and usb_wwan.ko for connection of 3G dongle, all nls charsets/codepages built as modules <--new to V2.2.2
    • V1.6.3 is pretty much V2.2.2 but without my custom ram disk. I've also tried a boot script method proposed by Toldo but haven't had time to test it yet. Please flash the CM9 stock kernel or Samsung stock kernel before trying V1.6.3.
    • Applied git patch to disable mmc_cap_erase <-- new to V1.6.4
    • Voltage control, cifs built in again <-- new to V1.7
    • Galaxy Tab 8.9 specific fix <--new to V1.7.1
    • Cyanogenmod charging mode fix <--new to V1.7.2
    • Galaxy Tab 8.9 specific feature <--new to V1.7.3
    • CM10 compatibility fix, enabled Samsung's powersaving governor <--new to V1.7.4
    • followed pershoot's "-defconfig: jb: unset TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND" change to fix odd 450MHz capping issue <--new to V1.7.4b
    • Copied in pershoot's keyboard dock driver <--new to V1.7.5
    • 801MB RAM enabled <-- new to V1.8
    • Rebased on pershoot's November 17 source <--new to V1.8.1
    • Back to samsung base, follow pershoot's suggestion of Nexus7 mtp drivers to fix mtp, enabled zRam <--new to V1.8.2
    • Reduced RAM to 785MB to prevent intense 3D games issue, enabled KSM (check in settings --> performance --> memory management)
    • (CM Version only) works on CM10.1 <--new to V1.8.4
    • Incorporated touchscreen death fix. Thank the user who reported it. <-- new to V1.8.5
    • Used part of pershoot's kernel config to get data usage working in CM <--new to V1.8.6
    • Added CM's version of the ROW (read over write) disk IO scheduler for GT-I9300<-- new to V1.8.7
    • Added XDA's grzwolf's solution to the hsic wakeclock problem <--new to V1.8.8
    • Added frandom kernel module <-- new to V1.9
    Credits:
    Supercurio: voodoo sound
    Pershoot: voodoo port, usb charging, flashable zip, OC template, current widget setup
    XDA forum's CazeW: used your replace suggestions to patch up wm8994_voodoo.c and wm8994_voodoo.h so it will compile properly, and finding the missing link for 1.4GHz OC, and disabling frequency locks
    Task650: providing a nice, clean deodexed rom for me to try this on
    XDA forum's RaymanFx: OC instructions
    Me: GPU OC
    XDA forum's jaswinky for valuable hints and checking my work over.
    Xoom ICS kernel: for getting an approximate idea of voltages
    (If I missed any credits, please forgive me as this is my first attempt at any kind of development)
    XDA forum's motley for voltage control
    XDA forum's Unknownzd for mmc_cap_erase patch
    XDA's grzwolf for the hsic wakelock fix
    11
    Very Good News

    So it looks like CM10.2 is actually alive and in testing on my tablet. Big thank you to user epinter for helping me with the graphics issue. I will play with CM10.2 to see how it is. First 10 seconds impression: buttery smooth, wifi works, bluetooth works, sound works, A1 kernel with SELinux firing on all cylinders! Unfortunately it has the 2 bar UI... time to search for that post on how to make tabletui.

    Please donate to epinter for CM10.2. He gets the credit for making it work. I just did some minor tweaking to the fstab and audio flinger.

    Gotta go to bed. Just check out the screenshot zips to see it working. I have no time adjust the sizes for xda.

    THE ZIP IS THE SCREENSHOTS, NOT THE ROM. I will post the rom later this week after testing.
    10
    Honeycomb Tablet Mode Partial Fix

    Hey everyone,

    I managed to figure out how to get the classic honeycomb tablet mode to work in CM10.1 (mostly). You know, the one where you get 1 status bar for the soft buttons and tray. Simply move the jars to /system/framework and the apk to /system/app. Do this with any root explorer or the terminal.

    I tried to make a flashable zip, but I managed to screw the permissions in the process and accidentally pull the plug on my computer, corrupting its data partition. I did setup my Linux install to have a system (/) and data partition (/home) like android.

    The only down side is that you can't customize the power widget but, on the upside, the UI seems noticeably less laggy than the stock CM10.1 UI with the 2 bars. Why??? Who knows. I think this benefit more than justifies the small annoyance of unchangeable toggles.

    Here are the instructions I followed: http://xdaforums.com/showpost.php?p=28957307&postcount=1, http://xdaforums.com/showpost.php?p=36319776&postcount=974.

    Last gotcha, it's for wifi only since that's what I have and I don't really want to wait for my computer to compile a whole other rom for the 3G version. (Have mercy on the Core2 mobile).
    8
    Great to see someone else kernel developing, could be the start of something here... Lol, I wanna give this a try but I think It'll stop 3G working if I flash the 7510 kernel.

    Sent from my GT-N7000 using Tapatalk 2

    Care to try the 3G version I just uploaded? I don't own the 3G version but I followed the same idea for compiling the 3G kernel.
    7
    Please do not advertise your roms in my kernel thread. This thread is mainly for bug reports and feature requests. Thank you for your understanding. (I did not advertise my A1 in pershoot's kernel thread saying "hey you want some of these features on stock rom, try my kernel". ) I will fix V2.0 to use a 3G ramdisk so 3G tablets will be able to use boot scripts later today.