[Kernel] Devil [4.3/4.2.2/4.1.2]- Linux 3.0.101 - Linaro 4.8.2 - Dualboot - 24/10

Search This thread

Herk718

Senior Member
Sep 7, 2010
910
343
New Jack City
exactly, that is the reason for the bootloops. didn't think of it. :(

now i need the help of a sprint users.
please use adb shell, or terminal app, to run this command:

ls -l dev/block

and psate the output here. thanks


u0_a105@android:/ $ su
u0_a105@android:/ # ls -l dev/block
brw------- root root 254, 1 2013-05-28 11:22 dm-1
brw------- root root 254, 2 2013-05-28 11:22 dm-2
brw------- root root 254, 3 2013-05-28 11:22 dm-3
brw------- root root 254, 4 2013-05-28 11:22 dm-4
brw------- root root 254, 5 2013-05-28 11:22 dm-5
brw------- root root 254, 6 2013-05-28 11:22 dm-6
brw------- root root 254, 7 2013-05-28 11:22 dm-7
brw------- root root 254, 8 2013-05-28 11:22 dm-8
brw------- root root 254, 9 2013-05-28 11:23 dm-9
brw------- root root 7, 0 2013-05-28 11:21 loop0
brw------- root root 7, 1 2013-05-28 11:21 loop1
brw------- root root 7, 2 2013-05-28 11:21 loop2
brw------- root root 7, 3 2013-05-28 11:21 loop3
brw------- root root 7, 4 2013-05-28 11:21 loop4
brw------- root root 7, 5 2013-05-28 11:21 loop5
brw------- root root 7, 6 2013-05-28 11:21 loop6
brw------- root root 7, 7 2013-05-28 11:21 loop7
brw------- root root 7, 8 2013-05-28 11:22 loop8
brw------- root root 7, 9 2013-05-28 11:23 loop9
brw------- root root 179, 0 2013-05-28 11:21 mmcblk0
brw------- root root 179, 16 2013-05-28 11:21 mmcblk0boot0
brw------- root root 179, 32 2013-05-28 11:21 mmcblk0boot1
brw------- root root 179, 1 2013-05-28 11:21 mmcblk0p1
brw-rw---- system radio 179, 10 2013-05-28 11:21 mmcblk0p10
brw-rw---- system radio 179, 11 2013-05-28 11:21 mmcblk0p11
brw------- root root 179, 12 2013-05-28 11:21 mmcblk0p12
brw------- root root 179, 13 2013-05-28 11:21 mmcblk0p13
brw------- root root 179, 14 2013-05-28 11:21 mmcblk0p14
brw------- root root 179, 15 2013-05-28 11:21 mmcblk0p15
brw------- root root 259, 0 2013-05-28 11:21 mmcblk0p16
brw------- root root 259, 1 2013-05-28 11:21 mmcblk0p17
brw------- root root 179, 2 2013-05-28 11:21 mmcblk0p2
brw------- root root 179, 3 2013-05-28 11:21 mmcblk0p3
brw-rw---- system radio 179, 4 2013-05-28 11:24 mmcblk0p4
brw-rw---- system radio 179, 5 2013-05-28 11:26 mmcblk0p5
brw-rw---- system radio 179, 6 2013-05-28 11:21 mmcblk0p6
brw-rw---- system root 179, 7 2013-05-28 11:21 mmcblk0p7
brw------- root root 179, 8 2013-05-28 11:21 mmcblk0p8
brw------- root root 179, 9 2013-05-28 11:21 mmcblk0p9
brw-rw---- root system 179, 48 2013-05-28 11:21 mmcblk1
brw------- root root 179, 49 2013-05-28 11:21 mmcblk1p1
lrwxrwxrwx root root 2013-05-28 11:21 param -> /dev/block/mmcblk0p7
drwxr-xr-x root root 2013-05-28 11:21 platform
brw------- root root 1, 0 2013-05-28 11:21 ram0
brw------- root root 1, 1 2013-05-28 11:21 ram1
brw------- root root 1, 10 2013-05-28 11:21 ram10
brw------- root root 1, 11 2013-05-28 11:21 ram11
brw------- root root 1, 12 2013-05-28 11:21 ram12
brw------- root root 1, 13 2013-05-28 11:21 ram13
brw------- root root 1, 14 2013-05-28 11:21 ram14
brw------- root root 1, 15 2013-05-28 11:21 ram15
brw------- root root 1, 2 2013-05-28 11:21 ram2
brw------- root root 1, 3 2013-05-28 11:21 ram3
brw------- root root 1, 4 2013-05-28 11:21 ram4
brw------- root root 1, 5 2013-05-28 11:21 ram5
brw------- root root 1, 6 2013-05-28 11:21 ram6
brw------- root root 1, 7 2013-05-28 11:21 ram7
brw------- root root 1, 8 2013-05-28 11:21 ram8
brw------- root root 1, 9 2013-05-28 11:21 ram9
drwx------ root root 2013-05-28 11:21 vold
u0_a105@android:/ #
 
  • Like
Reactions: DerTeufel1980

ztotherad

Senior Member
Aug 17, 2011
2,803
618
Illinois
OnePlus 9 Pro
nice! I've been using your other kernel for the t0lte and the recovery and dual booting with that. It's definitely nice to see the kernel officially for the vzw note II though. Thanks, DT. you freakin' rock!
 
  • Like
Reactions: andrewjt19

dawiseguy77

Senior Member
Dec 11, 2010
947
175
Can some one give a better explanation on "dual boot" please? Doe sit mean its works on aosp and twiz roms?
 

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
please try this kernel now. it should have support for sprint now (no dualboot obviously, as this needs the recovery).

please verizon users also try it, because i don't want to break it for you (which should not be the case) ;)

if this one is working for both, i start fixing the recovery.
 

Attachments

  • Devil-t0ltecdma-DUAL-0.21.1_20130528.zip
    6.8 MB · Views: 60
  • Like
Reactions: Herk718

DisposableHero1985

Senior Member
Sep 2, 2012
216
101
please try this kernel now. it should have support for sprint now (no dualboot obviously, as this needs the recovery).

please verizon users also try it, because i don't want to break it for you (which should not be the case) ;)

if this one is working for both, i start fixing the recovery.

new kernel boots all the way through but starts to loop at "Android is Upgrading"
 

ztotherad

Senior Member
Aug 17, 2011
2,803
618
Illinois
OnePlus 9 Pro
hey dt, I'm getting a "assert failed: write_raw_image("/tmp/recovery.img", "/dev/block/mmcblk0p9") E: Error in /external_sd/recovery/devil_dualboot_recovery-t0ltecdma.zip" (status 7) when flashing your recovery in cwm touch 6.0.32 on my vzw note II. Not sure what's causing it.


on a side note, it may be because I haven't flashed the cdma kernel yet, d'oh! :silly::eek:



EDITone: still getting the status 7 error on the cdma recovery even after flashing kernel
 

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668

DMardroid

Senior Member
Apr 15, 2012
738
319
Sunny So.Cal.
I flashed the kernel in op. Booted fine and all. When I went to boot in recovery again now Im bootlooping on the "Samsung galaxy note II" animation. Am I in trouble?

Sent from my Nexus 7 using Tapatalk 4 Beta
 

shangrila500

Senior Member
Jan 24, 2010
1,442
423
I flashed the kernel in op. Booted fine and all. When I went to boot in recovery again now Im bootlooping on the "Samsung galaxy note II" animation. Am I in trouble?

Sent from my Nexus 7 using Tapatalk 4 Beta


Try booting into recovery and wiping your cache and dalvik cache and see if that will fix the bootlooping. If not then you can either restore your nandroid or flash another kernel and that should fix it.

Sent from my SCH-I605 using XDA Premium HD app
 
  • Like
Reactions: DMardroid

DMardroid

Senior Member
Apr 15, 2012
738
319
Sunny So.Cal.
Try booting into recovery and wiping your cache and dalvik cache and see if that will fix the bootlooping. If not then you can either restore your nandroid or flash another kernel and that should fix it.

Sent from my SCH-I605 using XDA Premium HD app

Thanks. The problem is I can't boot in recovery now. Just keeps blinking on the "Samsung galaxy note 2" screen

Sent from my Nexus 7 using Tapatalk 4 Beta
 
  • Like
Reactions: idkwhothatis123

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
If the button combo doesn't work, you still can flash a recovery or kernel through odin

Gesendet von meinem GT-N7105 mit Tapatalk 2
 
  • Like
Reactions: DMardroid

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
What did you do in recovery. If there is a bug, I need as much information as possible to fix it

Gesendet von meinem GT-N7105 mit Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 91
    This Kernel is based off the sources of AndreiLux Perseus Kernel (alpha35).
    If you consider to thank me, please also consider to thank him http://xdaforums.com/showthread.php?t=1927852

    Features (changes compared to Perseus):
    - compiled with linaro gcc 4.8.2
    - updated Linux Kernel base to 3.0.101
    -zram, zsmalloc and lowmemorykiller updated from 3.9
    - DevilQ cpu governor (default)
    - block updated from Linux 3.3 (better i/o performance)
    - row i/o scheduler updated from Linux 3.4
    - fiops v2 i/o scheduler
    - working for Aosp and Sammy at once (Big thx to Gokhanmoral for making this possible)
    - Portet Ezekeel's Touchwake Feature (from nexus s)
    - Oc up to 2 Ghz
    - Backport from Linux 3.5 smp driver parts
    - Cm Wifi driver (from D2 Linux 3.4 kernel)
    - possibility to set high/low power mode for wifi when screen is off
    - LulzactiveQ cpu governor (from siyahkernel, thx again to Gokhanmoral)
    - Hotplug Cpu Governor
    - Proportional Rate Reduction for TCP
    http://kernelnewbies.org/Linux_3.2#head-1c3e71416a9fdc2f59c1c251a97963f165302b6e
    - improve memcopy/memmove
    - Using Voodoo Sound
    - mdnie: toggling mdnie negative effect with home button (Gokhanmoral)
    - Reverted LED Control
    - ExFat support (thx to samsung for opensourcing the driver)

    if your rom is based off PAC, Bam, Fusion, ... :
    IMPORTANT: As per notice of 01.11.2013, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you will receive a boot loop. Do not cry about this here but advise your Custom rom cooker to fix this. I will not change this ever again.
    The most prominent custom kernels for CM will follow the same approach (aligned between Yank555, Googy, LordBoeffla, Psndna, Temasek and me).

    So please do pass this message along to your favorite ROM devs.
    If they don't fix their rom, it won't be compatible with custom kernels any more!

    Kernel app http://xdaforums.com/showthread.php?p=41346443#post41346443



    Dualboot Faq:
    For more detailed instructions, please take a look at this thread from RichMd (thank you for it):
    Dualboot Faq thread

    Important: if you want to use this kernel for dualboot, i highly recommend flashing my recovery as well.

    General information about the recovery:
    dualboot menu.
    in this menu you can:
    * create the secondary system partition (needed to be run once, if you want to install a second rom)

    Install-zip menu:
    you'll notice there is a new menu, where to select what you want to flash.
    • if you select kernel, rom or recovery, the zip gets installed as it is.
    • if you select zipt to pri./sec. filesystem, it is selfexplanary
    • if you select rom to secondary fs, the zip gets modified to install to the sec. fs. IF YOU WANT TO INSTALL IT TO PRIMARY FS LATER SOME TIME, YOU NEED TO REDOWNLOAD THE FILE!
    • if you select rom to primary filesystem, it gets installed there, and you can use the same zip later again.

    How to install a second rom:
    make sure you have already created ssecondary system partition! if not, go to dualboot menu and create it now (this may take some minutes)
    • The savest way is the way by using nandroids: if you don't have a nandroid already, create one now. Then just select your backup, and restore it to secondary filesystem.
      you now should already be able to boot into primary or secondary rom (which are both the same now).
      now you can install any other rom as primary.
    • if you want to install a new rom directly as secondary,
      make sure there are no spaces in the filename!,
      then just go to install zip. you'll notice there's a new menu at some point.
      in this menu you can select where you want to install, and what type of file it is.
      if you choose rom to sec. fs, your zip files itself gets modified to be installed to secondary fs. this may take a minute, because the files needs to get zipped again. Imporant: this file is permanently modified. if you think you need it later again, you should redownload it, because the modified one would always install as secondary.

      installing a rom as primary, a zip to primary or zip to secondary fs, does not modify the zip.


    Additional information:
    • roms coming with an aroma installer are hard to handle, as every dev can place own commands into it. It's impossible for me, to take care of every possibility. Because of this, it should be the best method, to flash a rom with aroma installer as primary one (and then move it to secondary, by using the nandroid method, if you want it to be secondary).


    special greetings:
    to the guy in the general section who told me being kind of stupid, because NO kernel could boot aosp and tw at once :p
    I've never had a phone that could use the same kernel for both AOSP and touchwhiz/sense/motoblur/whatever.

    And I've had a lot of phones...
    :laugh::eek:


    Many Thanks to:
    - RichMD (I wouldn't have this device without him)
    - Gokhanmoral
    - Andreilux
    - DAGr8
    - simone201
    - ptmr3
    - Stratosk
    - RolloS
    - kasper_h
    - all the others mentioned in the changelogs
    21
    Changelog:

    24.10.2013
    + backport interacctive governor from googles linux 3.4 kernel source + enabled it
    + updated zzmove cpu governor
    + cpufreq: Save and restore min and max frequencies.
    + cpufreq: Save user policy min/max instead of policy min/max during hotplug
    + cpufreq: Only apply driver limits for scaling_min/max_freq writes
    + linux 3.0.101 (last update)

    22.10.2013
    + revert: zram: use zram->lock to protect zram_free_page() in swap free notify path
    + added support for latest cm nightlies
    + some cleanup by removing non used code

    20.10.2013
    + linux 3.0.100
    + added support for pac rom
    + reverted some autohotplug related commits which aren't useful if there are only governors with own hotplug logic
    + reverted cpu oc from 2000 to 1800 (stability testing in connection to undervolting)
    + zram: use zram->lock to protect zram_free_page() in swap free notify path (thx to stsdema28 for suggeting this patch)
    + some patches to improve general swap performance (especially zram)
    + minor update to block kernel subsystem (io schedulers)

    03.10.2013
    + linux 3.0.98
    + fixed zram kernel crashes
    + fixed triangle away (thx ckh469)
    + memcopy improvement (also thx to ckh469)

    30.09.2013
    + linux 3.0.97
    + added additional sysfs for controling vibration on 4.2.2 roms by using device settings or devil tools
    + zram: re-added code for using multiple cores for (de)compression, which should be significantly faster now
    + zram: upstreamed to linux 3.12
    + zcache: fix booting by syncing code with faux123
    + re-enabled cleancache
    + block/io-schedulers: big update to row and cfq scheduler from linux 3.4 (thx to andreilux for squashing the commits)
    + fixed adb root options after data wipe
    + added options to turn of hardwarekeys backlight on screen touch, thx to yank555-lu (for now, this isn't added to deviltools, please see below for the sysfs path/command)
    this doesn't affect samsung roms!
    * /sys/class/sec/sec_touchkey/touch_led_handling (rw)
    *
    * 0 - handled by ROM (newer CM10.2, default)
    * 1 - handled by kernel (older CM10.2)
    *
    * /sys/class/sec/sec_touchkey/touch_led_on_screen_touch (rw)
    *
    * 0 - hardware keys backlight only lights up if h/w keys are used
    * 1 - hardware keys backlight lights up if h/w keys are used or screen is touched (default)

    18.08.2013
    - added exfat support
    - support for android 3.4 (only primary rom or single boot)
    - linux 3.0.91

    10.08.2013
    - fixed sysfs of led control to be readable/writable by deviltools
    - re fixed mtp/ums and adb root

    09.08.2013
    - backported zram_for_android from linux 3.4 (i9500) and enabled it again
    - updated zram to latest official version (linux 3.11
    - updated android binder driver
    - added led control by yank555-lu

    05.08.2013
    - linux 3.0.89
    - disabled uksm (cam failure on i9300)
    - updated/backported zsmalloc, zram and lowmemorykiller from 3.9 (disabled zcache and zram_for_android because of this)
    - fixed a bug in ashem driver, caused by samsung, which could lead to deadlocks
    - mmc: fix the workqueue overload battery waste (thx to aagit)
    - fixed adb root
    - fixed mtp/ums issues after wipe

    31.07.2013
    - updated to linux 3.0.88
    - added andreilux's abb control
    - updated and activated zram (thx to yank555), zcache, cleancache and frontswap (most probably not very important on note2)
    - enabled uksm by default (http://www.phoronix.com/scan.php?page=news_item&px=MTEzMTI)
    - added experimental support for android 4.3 (only i9300 for now)
    - reduced wifi wakelocks a little bit more

    25.0.7.2013
    - cpufreq: zzmoove governor 0.6 (thx to zanezam)
    - include most of touchwake 1.1 changes. thanks to yank555-lu
    - bcmdhd: update back to version used by andreilux. …
    big thx to xda forum member gondsman: http://xdaforums.com/member.php?u=3740419 (this should drastically reduce wifi wakelocks)

    24.07.2013
    - reverted compiler option "optimze_for_size" to fix cam on aosp roms

    23.07.2013
    reverted wifi driver to cm version, to fix wifi tethering, additional disabled multicast in suspend for power savings

    22.07.2013
    - linux 3.0.86
    - disable touchwake during call
    - se linux support
    - wifi driver from andreilux sammy kernel (should reduce wakelocks)

    recovery:
    - reduced font size
    - updated latest changes from philz and cm
    - fixed creation of secondary system.img

    27.06.2013
    - linux 3.0.83
    - fixed mounting of internal sdcard on secondary 4.2.2 aosp roms
    - reverted JRcu
    - dyn fsync updates from faux123
    - two upstream fixes to row i/o scheduler
    - added latest cm changes (UMS: f_mass_storage: Added cdrom option to UMS-lun-devices, Samsung i9300 Update 10)

    12.06.2013
    - linux 3.0.81
    - fixed dualboot recovery for cdma
    - fixed internal storage on 4.2.2 secondary roms
    - reverted cpufreq driver back to "default", to try fixing being stuck at max. freq for some users
    - merged update9 changes from cm team
    - wifi changes which hopefully reduce wakeup time
    - built nfs as module (was built-in before)

    29.05.2013
    - update to linux 3.0.80
    - reverted a commit from 3.0.79 which caused the cpu to be stuck at max. freq
    - fix touchwake/proximity sensor for i9300
    - cpufreq: fix handling of offline cpus
    - dynamic fsync: fixes from faux123, to prevent data loss, in case of kernel panic/unexpected shutdown
    - CPU hotplug, writeback: Don't call writeback_set_ratelimit() too often during hotplug (from francisco franco)
    - freezer: allow tasks to be frozen faster (1ms if possible, instead of 10 ms)
    - freezer: skip waking up tasks with PF_FREEZER_SKIP set, to make suspend/resume more efficient
    - t0ltecdma: fixed sprint compatibility

    15.05.2013

    important: please uncheck in deviltools to apply settings on boot! gpu voltage changes would cause the device to freeze on startup!

    - reverted gpu voltage to be displayed as before (this fixes incompatibility with trickstermod or other apps)
    - DevilQ: turn/keep second core online on screen touch
    - add PM_SUSPEND_FREEZE powerr state (if used, it does save little less power, but PM_SUSPEND_FREEZE has less resume latency
    •Erik Gilling - sync: don't log wait timeouts when timeout = 0
    •Ørjan Eide - sync: Fix race condition between merge and signal
    •Erik Gilling - sync: add Documentation/sync.txt
    •Erik Gilling - sync: add tracepoint support
    •Erik Gilling - sync: refactor sync debug printing
    •Erik Gilling - sync: use proper barriers when waiting indefinitely
    •Erik Gilling - sync: update new fence status with sync_fence_signal_pt
    •Erik Gilling - sync: protect unlocked access to fence status
    •Erik Gilling - sync: dump sync state of fence errors
    •Erik Gilling - sync: improve timeout dumps
    •Erik Gilling - sync: use correct signed type when handling SYNC_IOC_WAIT
    •Erik Gilling - sync: dump sync state to console on timeout
    •Erik Gilling - sync: clean up compiler warnings
    •Erik Gilling - sync: fix erase-o in sync_fence_wait
    •Erik Gilling - sync: change wait timeout to mirror poll semantics
    •Rebecca Schultz Zavin - sync: Fix error paths
    •Erik Gilling - sync: add reference counting to timelines
    •Erik Gilling - sync: add internal refcounting to fences
    •Erik Gilling - sync: optimize fence merges
    •Erik Gilling - sync: reorder sync_fence_release
    •Erik Gilling - sync: export sync API symbols
    •Erik Gilling - sync: allow async waits to be canceled
    - ext4: prevent kernel panic in case of uninitialized jinode
    - mutex: dynamically disable mutex spinning at high load Date Thu, 4 Ap… … (faux123)
    - mutex: restrict mutex spinning to only one task per mutex … (Waiman Long)
    - mutex: Make more scalable by doing less atomic operations … (Waiman Long)
    - hrtimer: Prevent enqueue of hrtimer on dead CPU When switching the hr… … (franciscofranco)
    - hrtimer: Consider preemption when migrating hrtimer cpu_bases When sw… … (franciscofranco)
    - fs/buffer.c: remove redundant initialization in alloc_page_buffers() … … (clouds-yan)
    - time: cast ->raw_interval to u64 to avoid shift overflow We fixed a b… … (faux123)
    - vmscan: comment too_many_isolated() Comment "Why it's doing so" rathe… … (Wu Fengguang)
    - mm/vmscan.c: avoid possible deadlock caused by too_many_isolated() Ne… … (Wu Fengguang)
    - input: evdev: Move wake_lock_destroy call … (halaszk)
    - wakelock: use single threaded workqueueus … (halaszk)

    12.05.2013
    - linux 3.0.78
    - added own cpu governor, DevilQ (based off lulzactiveq by gokhanmoral)
    - improved touchwake (acting like swipe2wake now, if delay is set to 0, to prevent false wake ups)
    - pegasusq: readd some of andreilux's changes
    - gpu: allow oc up to 800 mhz
    - added option to disable touch boost
    - updated wifi driver from s4 (commit by cm team)
    - disabled swap, zram and cleancache

    28.04.2013
    - linux 3.0.75
    - fixed cam preview on note2 lte
    - new tunables for pegasusq:
    * early_demand: to enable this functionality (disabled by default). ( echo 1 > sys/devices/system/cpu/cpufreq/pegasusq/early_demand, to enable it. 0 disables it)
    * grad_up_threshold: over this gradient of load we will increase
    frequency immediately. ( echo xx > sys/devices/system/cpu/cpufreq/pegasusq/grad_up_threshold, to set value. xx has to be betwenn 11 and 100, default 50)

    27.04.2013
    - updated block to linux 3.3
    - updated row i/o scheduler to linux 3.4
    - added fiops v2 i/o schedler

    25.04.2013
    - readded gokhanmorals sammy/aosp mod more cleanly
    - lulzactiveq: small fixes
    - cpufreq_pegasusq.c: revert to stock
    - Enabled AIO support
    - improved aio: Asynchronous I/O latency to a solid-state disk greatly increased between the 2.6.32 and 3.0 kernels. By removing the plug from do_io_submit(), we observed a 34% improvement in the I/O latency.
    - added zzmoove governor

    - Andreilux:
    * mdnie-control: Digital brightness control
    * s6e8aa0: Allow manual brightness to 300 candela
    * ARM: decompressor: Enable unaligned memory access for v6 and above


    19.04.2013:
    - Fixed patch: "LOAD_FREQ (4.61 s) avoids loadavg Moire (thx to Klaus Ripke)", many thx to AndreiLux for pointing and fixing this
    - Added Franciscofranco's Touch Boost Control (input boost frq., when screen touched can be set with trickster mod app), including the additions from simone201, but fixed to not beeing stuck at high freq.
    - removed LCDFreq scaling mechanism (using touch boost instead)
    - fixed charging while device off
    - applied a bluetooth patch from cm (might help with bt issues some users were reporting)

    more to come ...
    16
    here we go:

    + updated linux to latest 3.0.96
    + Revert "wakelock: use single threaded workqueueus" (supposed to fix android os bug)
    + compiled using linaro 4.8.2 gcc
    + surprise (many thanks to umberto1978 for this)
    14
    new kernel in the op :)
    10
    New build uploaded :)

    Gesendet von meinem GT-N7105 mit Tapatalk 2