Related
Github:
I now consider this Release Candidate quality. Please do report issues (with logcats and dmesgs). Check the known bugs, etc, etc.
https://github.com/s0be/cm-kernel
the -amonra zip is for recoveries that don't take the FS type as the first argument of mount(...) If the regular zip fails complaining about missing files, try the -amonra version.
Latest official version:
no debug
http://heroc.s0be.com/HERC-2.6.35-AP-5.zip
http://heroc.s0be.com/HERC-2.6.35-AP-5-amonra.zip
Headset detection less broken. Now it always thinks there's a mic connected to anything plugged in.
http://heroc.s0be.com/HERC-2.6.35-AP-4.zip
http://heroc.s0be.com/HERC-2.6.35-AP-4-amonra.zip
If that download doesn't work for you, your OS likely has a broken ipv6 stack. Please check that you have ipv6 disabled if you don't actually have an ipv6 connection.
What works:
Ram console
Keypad
Screen
Touchscreen
GPS
Compass
G-Sensor
nand
Early Suspend
Bluetooth
Headset Detection
Camera
What Doesn't work or hasn't been tested:
Thanks to:
Elemag for the initial Hero 2.6.35 port, with Erasmux as a major contributor, Decadence for the 2.6.34/35 heroc board files, and riemervdzee for his pointers at fixes needed to get it working and his continued drive to get this kernel full featured and stable, and everyone they pulled from (Darch, Toast, Cyanogen, etc, etc). If I've forgotten anyone, please let me know the names to add.
See first post for current. This is just historic releases.
Headset detection fixed. Mic detection not working yet.
Weird audio program related crashes fixed
http://heroc.s0be.com/HERC-2.6.35-AP-3.zip
http://heroc.s0be.com/HERC-2.6.35-AP-3-amonra.zip
Rebased on Pershoot's G1 2.6.35.11 Kernel Tree
New base .config
BFS Disabled
Headset detection re-broken. Will be reviewing this currently.
http://heroc.s0be.com/HERC-2.6.35-AP-2.zip
http://heroc.s0be.com/HERC-2.6.35-AP-2-amonra.zip
Camera fix from JayBob via decad3nce
http://heroc.s0be.com/HERC-2.6.35-AP-1.zip
http://heroc.s0be.com/HERC-2.6.35-AP-1-amonra.zip
Pulls some changes from Decad3nce for the camera (still doesn't work) and some i2c speedups from riemervdzee
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-114.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-114-amonra.zip
Fixes most of what I broke in 106
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-109.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-109-amonra.zip
Disabled some ****
Changed some ****
This is an attempt to fix the power issues through voodoo
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-106.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-106-amonra.zip
Fixed headset detection. Haven't figured out if the button works.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-101.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-101-amonra.zip
Went back to #55(never released) config
Disabled Debug
All updates from #56 still apply
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-57.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-57-amonra.zip
Merged with upstream
Updated msm-camera
Updated msm-i2c
Ripped out a bunch of stuff, disabled debugging
This probably isn't going to be completely happy
This is definitely not happy...
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-56.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-56-amonra.zip
Restored device mapper with crypt support. This may fix missing app issues
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-47.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-47-amonra.zip
tun.ko Enabled - NOT TESTED AT ALL, PLEASE REPORT IF I GOT IT RIGHT
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-45.zip
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-45-amonra.zip
Enabled > 6912000 CPU speeds. Boots capped at 691 though
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-44.zip
Fix ramzswap/compcache
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-42-2.zip
h2w still broken
Camera almost works
Bluetooth is fixed
Touchscreen may not be problematic now.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-42.zip
Merged MDP changes from upstream
Fixed h2w (I think) someone with a headset, try plugging it
Camera almost works on occasion. Can catch a preview frame now and then.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-30.zip
Re-enabled netfilter modules
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-23.zip
changed the early_suspend.level value of the synaptics_i2c_rmi driver to match 2.6.29.
Last attempt til next week
still capped at 691200
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-18.zip
Clamped to 691200 max freq
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-17.zip
Maybe solved TS issues??? Testing now.
Fixed USB Mass Storage
Enabled PerfLock
CURRENT MAX IS AT 768000, throwing together a #14 with a 691200 cap.
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-13.zip
First alpha
http://heroc.s0be.com/HERC-2.6.35-sl0ppy_s0be-5.zip
what kind of performance increase will this bring? and will it be nice to have when we get a fully working GB rom?
Unfortunally the current .35 build for the Hero GSM version is slower than any .29 kernel.
But yeah, seems we have to reimplement a lot of optimalisations.
It is nice that we actually get something out of the HeroC though
riemervdzee said:
Unfortunally the current .35 build for the Hero GSM version is slower than any .29 kernel.
But yeah, seems we have to reimplement a lot of optimalisations.
It is nice that we actually get something out of the HeroC though
Click to expand...
Click to collapse
There are other advantages of course, we have to remember. Performance is king, but features are definitely queen. Getting to a recent kernel (2.6.29 is coming up on 2 years old), makes future updates to Heroc a lot easier. Going to up-to-date drivers may allow us to eliminate some of the binary cruft from the Heroc tree, etc, etc.
Two things I've tried:
1. In the xda "hero" dev forum, there was a post that there was a problem with the newer (>.34) yaffs2 code, and you needed to boot and wipe using a 1.7 RA recovery. So, I copied the yaffs2 code from deca's .29 kernel. It then oopsed at 1017 in msm_fb, which was the ifdef'd line for HERO.
2. So, I added "&& !defined(CONFIG_MACH_HEROC)" to line 1016. It then still rebooted, but last_kmsg was different after "vsync on gpio 97 now 0":
[ 3.626831] vsync on gpio 97 now 0
[ 3.632263] msmfb_probe() installing 320 x 480 panel
[ 3.640106] Registered led device: lcd-backlight
[ 3.650085] msm_serial: driver initialized
[ 3.654052] msm_serial_hs module loaded
[ 3.697570] loop: module loaded
[ 3.698760] pmem: 1 init
[ 3.702514] pmem_adsp: 0 init
[ 3.706420] pmem_camera: 0 init
[ 3.711578] Android kernel panic handler initialized (bind=kpanic)
[ 3.712524] AKM8973 compass driver: init
[ 3.718566] input: compass as /devices/virtual/input/input0
[ 3.731079] msm_nand: allocated dma buffer at ffa0a000, dma_addr 256fb000
[ 3.732696] msm_nand: read CFG0 = aa5400c0 CFG1 = 8744a
[ 3.733245] msm_nand: CFG0 cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4
[ 3.734069] msm_nand: NAND_READ_ID = 5501bcec
[ 3.735229] msn_nand: nandid 5501bcec status c03120
[ 3.735595] msm_nand: manuf Samsung (0xec) device 0xbc blocksz 20000 pagesz 800 size 20000000
[ 3.736114] msm_nand: save CFG0 = e85408c0 CFG1 = 4745e
[ 3.736419] msm_nand: CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=0 num_addr_cycles=5
[ 3.737121] msm_nand: DEV_CMD1: f00f3000
[ 3.737609] msm_nand: NAND_EBI2_ECC_BUF_CFG: 1ff
[ 3.738372] 6 cmdlinepart partitions found on MTD device msm_nand
[ 3.738708] Creating 6 MTD partitions on "msm_nand":
[ 3.739257] 0x00001ff60000-0x000020000000 : "misc"
[ 3.753509] 0x000002c60000-0x000003160000 : "recovery"
[ 3.776397] 0x000003160000-0x0000033e0000 : "boot"
[ 3.794219] 0x0000033e0000-0x000009be0000 : "system"
[ 4.070312] 0x000009be0000-0x000009fe0000 : "cache"
[ 4.098876] 0x000009fe0000-0x000020000000 : "userdata"
No errors detected
Don't know if this helps or not. BTW, I'm using Firerats's custom MTD partitions, so I modified the boot parameters.
dbayub said:
Two things I've tried:
1. In the xda "hero" dev forum, there was a post that there was a problem with the newer (>.34) yaffs2 code, and you needed to boot and wipe using a 1.7 RA recovery. So, I copied the yaffs2 code from deca's .29 kernel. It then oopsed at 1017 in msm_fb, which was the ifdef'd line for HERO.
2. So, I added "&& !defined(CONFIG_MACH_HEROC)" to line 1016. It then still rebooted, but last_kmsg was different after "vsync on gpio 97 now 0":
<SNIP>
Don't know if this helps or not. BTW, I'm using Firerats's custom MTD partitions, so I modified the boot parameters.
Click to expand...
Click to collapse
yeah, I had that fixed in my tree, forgot to commit the || -> && change I didn't do that yaffs2 change, but I just tested it with identical results.
Sweet. I'll spend more time on it this weekend. Swamped with homework atm.
Hopefully we'll have something super stable!
Decad3nce said:
Sweet. I'll spend more time on it this weekend. Swamped with homework atm.
Hopefully we'll have something super stable!
Click to expand...
Click to collapse
Made some more progress:
http://android.pastebin.com/AWysQDNk
s0be, i think you're going to blow up the hero scene again. with deca and you working together there's been a lot of progress recently and i want to thank both of you. i really love my hero and you guys keep it feeling young.
AND HOW!!!!!
Sent from my HERO200 using XDA App
jmkarnai01 said:
AND HOW!!!!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
More commits
More Progress
http://android.pastebin.com/rqm0Vn1p
You guys are pure AWESOME!
S0be, i was wondering your opinion, once this kernel is completed and we get GB running smoothly, will the supposed 2.4 GB update break everything that is already working or just maybe the new stuff will have to be worked in properly?
Pocker09 said:
S0be, i was wondering your opinion, once this kernel is completed and we get GB running smoothly, will the supposed 2.4 GB update break everything that is already working or just maybe the new stuff will have to be worked in properly?
Click to expand...
Click to collapse
no clue
http://android.pastebin.com/SSRM5MKB
Dang sobe making progress good work man. Thanks!!!!!!!!!!!"!
Sent from my HTC Hero CDMA using XDA App
oostah said:
Dang sobe making progress good work man. Thanks!!!!!!!!!!!"!
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
http://android.pastebin.com/qKr6wEtY
Some more progress, looks like just the smd and i2c errors are left to fix
Looking forward to this. And wow you work like super man lol but thank for the time and hard work.
Root-Hack-Mod-Always™
Just curious, will you guys be running AOSP's GB or will this kernel allow for a less tweaked version of GB? Thanks! Great Job!
The smd stuff is because it used to call both v1 and v2 alloc, and as long as one succeeded, it was OK. Now it's ifdef'd to use different code depending on if CONFIG_MSM_SMD_PKG3 is set or not. Looks like the package 4 code is what works on heroc. With that change, the smd code works.
[ 3.684967] smd_alloc_channel() cid=01 size=08192 'SMD_DIAG'
[ 3.686340] smd_alloc_channel() cid=02 size=08192 'SMD_RPCCALL'
etc. Then it's the i2c failures:
[ 3.841674] msm_i2c msm_i2c.0: Error during data xfer 1e (-5)
[ 3.852203] msm_i2c msm_i2c.0: error, status 63c8
and oops:
[ 4.861785] Internal error: Oops: 80000005 [#1] PREEMPT
[ 4.863433] last sysfs file:
[ 4.864318] Modules linked in:
[ 4.866058] CPU: 0 Not tainted (2.6.35.10-cyanogenmod #11)
[ 4.867706] PC is at 0x0
[ 4.868682] LR is at microp_i2c_probe+0xb70/0x1438
[ 4.869598] pc : [<00000000>] lr : [<c0217e64>] psr: 60000013
[ 4.869659] sp : cc219e10 ip : cc219d10 fp : cc219e74
[ 4.872100] r10: c040eef4 r9 : 00000000 r8 : 00000005
[ 4.873748] r7 : cc255da0 r6 : c040ea10 r5 : cc255d80 r4 : cc48a760
[ 4.874694] r3 : c040ea2c r2 : 00000002 r1 : cc219ce0 r0 : cc219e3c
[ 4.876342] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
I run CROMI-X 4.6.9 with hundsbuah 3.0.6 Kernel with Data2SD mod. I tried to run premium version of LagFix and it said that Trim is not supported on any partition. It always worked perfectly fine, so what is wrong?
Arquiteto said:
I run CROMI-X 4.6.9 with hundsbuah 3.0.6 Kernel with Data2SD mod. I tried to run premium version of LagFix and it said that Trim is not supported on any partition. It always worked perfectly fine, so what is wrong?
Click to expand...
Click to collapse
No idea I run Lagfix fine on CROMi-X. I haven't tried it on hunds but I will now and let you know.
sbdags said:
No idea I run Lagfix fine on CROMi-X. I haven't tried it on hunds but I will now and let you know.
Click to expand...
Click to collapse
Well. This is not a kernel issue. I flashed _that3 kernel and tried it, then I went back to hunds - both time when I run LagFix my tf700 rebooted. After reboot I tried again and then got "TRIM not supported by \cache, \data partition". Might this be problem with ext2 partition of my MicroSD?
Arquiteto said:
Well. This is not a kernel issue. I flashed _that3 kernel and tried it, then I went back to hunds - both time when I run LagFix my tf700 rebooted. After reboot I tried again and then got "TRIM not supported by \cache, \data partition". Might this be problem with ext2 partition of my MicroSD?
Click to expand...
Click to collapse
Just ran it on hunds and that v4 and it worked fine on both so something else is causing the conflict and the reboot. Grab the last_kmsg from /proc directly after such a reboot and post it so we can see what it was doing when it rebooted.
Well, I'm surprised too as it always worked for me.
Code:
[ 2281.200283] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:738: group 106, 32253 blocks in bitmap, 32254 in gd
[ 2281.200715] Kernel panic - not syncing: EXT4-fs (device mmcblk1p2): panic forced after error
[ 2281.200728]
[ 2281.201185] [<c00182dc>] (unwind_backtrace+0x0/0x144) from [<c096ec68>] (dump_stack+0x20/0x24)
[ 2281.201475] [<c096ec68>] (dump_stack+0x20/0x24) from [<c0970f28>] (panic+0x94/0x1c4)
[ 2281.201780] [<c0970f28>] (panic+0x94/0x1c4) from [<c023ae7c>] (ext4_handle_error.part.115+0x70/0xa8)
[ 2281.202071] [<c023ae7c>] (ext4_handle_error.part.115+0x70/0xa8) from [<c023c744>] (__ext4_grp_locked_error+0xe4/0x1d8)
[ 2281.202359] [<c023c744>] (__ext4_grp_locked_error+0xe4/0x1d8) from [<c024eeb8>] (ext4_mb_generate_buddy+0x140/0x290)
[ 2281.202526] [<c024eeb8>] (ext4_mb_generate_buddy+0x140/0x290) from [<c02519e4>] (ext4_mb_init_cache+0x85c/0xc68)
[ 2281.202805] [<c02519e4>] (ext4_mb_init_cache+0x85c/0xc68) from [<c0251ecc>] (ext4_mb_init_group+0xdc/0x108)
[ 2281.203085] [<c0251ecc>] (ext4_mb_init_group+0xdc/0x108) from [<c02587a8>] (ext4_trim_fs+0x31c/0x330)
[ 2281.203373] [<c02587a8>] (ext4_trim_fs+0x31c/0x330) from [<c0227740>] (ext4_ioctl+0x5f0/0x86c)
[ 2281.203664] [<c0227740>] (ext4_ioctl+0x5f0/0x86c) from [<c018759c>] (do_vfs_ioctl+0x8c/0x2e0)
[ 2281.203943] [<c018759c>] (do_vfs_ioctl+0x8c/0x2e0) from [<c0187838>] (sys_ioctl+0x48/0x6c)
[ 2281.204115] [<c0187838>] (sys_ioctl+0x48/0x6c) from [<c00100c0>] (ret_fast_syscall+0x0/0x30)
[ 2281.204529] CPU2: stopping
[ 2281.204709] [<c00182dc>] (unwind_backtrace+0x0/0x144) from [<c096ec68>] (dump_stack+0x20/0x24)
[ 2281.204994] [<c096ec68>] (dump_stack+0x20/0x24) from [<c00085e4>] (do_IPI+0x208/0x218)
[ 2281.205273] [<c00085e4>] (do_IPI+0x208/0x218) from [<c000fbf8>] (__irq_svc+0x38/0xd0)
[ 2281.205422] Exception stack(0xc78d3ee8 to 0xc78d3f30)
[ 2281.205692] 3ee0: c78d3f38 10624dd3 00000000 000f4240 00006f5f 00000000
[ 2281.205967] 3f00: c7ac9c00 c7ac9c70 1fbe3005 00000213 c0df9384 c78d3f64 00000000 c78d3f30
[ 2281.206119] 3f20: c03b2168 c005be20 20000153 ffffffff
[ 2281.206410] [<c000fbf8>] (__irq_svc+0x38/0xd0) from [<c005be20>] (tegra_idle_enter_lp2.part.2+0xb8/0x114)
[ 2281.206692] [<c005be20>] (tegra_idle_enter_lp2.part.2+0xb8/0x114) from [<c005bef0>] (tegra_idle_enter_lp2+0x74/0x78)
[ 2281.206981] [<c005bef0>] (tegra_idle_enter_lp2+0x74/0x78) from [<c068420c>] (cpuidle_idle_call+0x114/0x38c)
[ 2281.207150] [<c068420c>] (cpuidle_idle_call+0x114/0x38c) from [<c00113d0>] (cpu_idle+0xd4/0x11c)
[ 2281.207434] [<c00113d0>] (cpu_idle+0xd4/0x11c) from [<c096bf48>] (secondary_start_kernel+0x154/0x158)
[ 2281.207719] [<c096bf48>] (secondary_start_kernel+0x154/0x158) from [<8096b814>] (0x8096b814)
[ 2281.207995] Rebooting in 10 seconds..
[ 2291.220771] Restarting Linux version 3.1.10-hundsbuah-v3.0.6-oc ([email protected]) (gcc version 4.6.3 (Sourcery CodeBench Lite 2012.03-56) ) #1 SMP PREEMPT Mon May 13 18:42:19 CEST 2013
[ 2291.220794]
No errors detected
May it be that LagFix is trying to trim ext4 fs while this is really ext2?
What comes before this bit?
[2281.200283] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:738: group 106, 32253 blocks in bitmap, 32254 in gd
[2281.200715] Kernel panic - not syncing: EXT4-fs (device mmcblk1p2): panic forced after error
Here is whole last_kmsg:
http://db.tt/TYhb9rUF
I pasted everything that seemed important, but I'm not an expert. It looked like regular jobs.
Arquiteto said:
Here is whole last_kmsg:
http://db.tt/TYhb9rUF
Click to expand...
Click to collapse
[ 2281.200283] EXT4-fs error (device mmcblk1p2): ext4_mb_generate_buddy:738: group 106, 32253 blocks in bitmap, 32254 in gd
Your filesystem metadata is inconsistent. Information about free blocks is stored twice in the filesystem - in a bitmap to track free blocks one by one, and as a number per blockgroup to quickly find groups with free blocks. Here, the filesystem has detected an inconsistency between those two.
Fix: run fsck on the partition. Since it's mounted in Android, either use an external card reader on a PC, or run fsck from the recovery.
_that said:
Fix: run fsck on the partition. Since it's mounted in Android, either use an external card reader on a PC, or run fsck from the recovery.
Click to expand...
Click to collapse
I run fsck through adb in recovery and now everything is working fine. Thank you
Hi,
I'm working on completely different hardware, but I have such errors all the time.
_that said:
Your filesystem metadata is inconsistent. Information about free blocks is stored twice in the filesystem - in a bitmap to track free blocks one by one, and as a number per blockgroup to quickly find groups with free blocks. Here, the filesystem has detected an inconsistency between those two.
Click to expand...
Click to collapse
My question is, what is cause of such filesystem corruption?
What can I do to avoid this?
Using no journal?
Or maybe I did something wrong with the partitioning?
Or there is bad voltage/speed of eMMC memory?
_that said:
Fix: run fsck on the partition. Since it's mounted in Android, either use an external card reader on a PC, or run fsck from the recovery.
Click to expand...
Click to collapse
What to do, if there isn't CWM and recovery has no fsck option (or will have no such option for user)?
Hi,
I recently bought a Nexus 5 in Antwerp, Belgium (about three weeks ago). The build number is KOT49H. The first few days I didn't receive a reboot but after downloading a couple of apps, my phone rebooted about 4 to 5 times a day. I decided to RMA the phone and since an employee from the store I bought it from said I didn't need to store it back to original settings I just deleted my personal information and some apps. Then the reboots just weren't as active as before, I received one or two that week and decided to just let it slide for another week or so. Now I rooted my phone for viper4android and to check the last_kmgs files and noticed the reboots are because of kernel panic.
[ 2591.876665] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 2591.876667]
[ 2591.876788] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09ffa4c>] (dump_stack+0x20/0x24)
[ 2591.876864] [<c09ffa4c>] (dump_stack+0x20/0x24) from [<c0a0045c>] (panic+0x9c/0x21c)
[ 2591.876940] [<c0a0045c>] (panic+0x9c/0x21c) from [<c030f2d8>] (__ext4_abort+0xe0/0xf4)
[ 2591.876984] [<c030f2d8>] (__ext4_abort+0xe0/0xf4) from [<c030f664>] (ext4_journal_start_sb+0xa0/0x1a4)
[ 2591.877063] [<c030f664>] (ext4_journal_start_sb+0xa0/0x1a4) from [<c02fcb0c>] (ext4_rename+0x48/0x728)
[ 2591.877143] [<c02fcb0c>] (ext4_rename+0x48/0x728) from [<c0273334>] (vfs_rename+0x350/0x4c4)
[ 2591.877219] [<c0273334>] (vfs_rename+0x350/0x4c4) from [<c027366c>] (sys_renameat+0x1c4/0x1d4)
[ 2591.877295] [<c027366c>] (sys_renameat+0x1c4/0x1d4) from [<c02736a8>] (sys_rename+0x2c/0x30)
[ 2591.877341] [<c02736a8>] (sys_rename+0x2c/0x30) from [<c0107300>] (ret_fast_syscall+0x0/0x30)
[ 2592.877756] Rebooting in 5 seconds..
[ 2597.879359] Going down for restart now
[ 2597.880123] Calling SCM to disable SPMI PMIC arbiter
No errors detected
Boot info:
Last boot reason: kernel_panic
Click to expand...
Click to collapse
It also seems the reboots are almost always in the weekend when I am at my mother's house (in the week I live in a student room).
So if anyone has some advice or needs more information, just ask.
Thanks a lot.
Niurez said:
Hi,
I recently bought a Nexus 5 in Antwerp, Belgium (about three weeks ago). The build number is KOT49H. The first few days I didn't receive a reboot but after downloading a couple of apps, my phone rebooted about 4 to 5 times a day. I decided to RMA the phone and since an employee from the store I bought it from said I didn't need to store it back to original settings I just deleted my personal information and some apps. Then the reboots just weren't as active as before, I received one or two that week and decided to just let it slide for another week or so. Now I rooted my phone for viper4android and to check the last_kmgs files and noticed the reboots are because of kernel panic.
It also seems the reboots are almost always in the weekend when I am at my mother's house (in the week I live in a student room).
So if anyone has some advice or needs more information, just ask.
Thanks a lot.
Click to expand...
Click to collapse
Well..... If you had a phone and these problems happened because of "apps and viper4android" and then you got another phone and did the same thing and get the same result then it is obviously something you are doing. Did it do this before you loaded your apps and viper4android? What method did you use to root/ how did you do it? I highly doubt the time of the week has anything to do when it reboots but I could be wrong.
A kernel panic is defined as "A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover."
You are obviously doing something that it does not like.
I searched some of the lines of code and compared it to this thread here: http://forum.xda-developers.com/showthread.php?t=2553949
Try loading a different kernel. It doesn't matter anyone and see if that fixes the problem, you are rooted so it should take three minutes.
mistahseller said:
Well..... If you had a phone and these problems happened because of "apps and viper4android" and then you got another phone and did the same thing and get the same result then it is obviously something you are doing. Did it do this before you loaded your apps and viper4android? What method did you use to root/ how did you do it? I highly doubt the time of the week has anything to do when it reboots but I could be wrong.
Click to expand...
Click to collapse
Well it started before I rooted the phone. The apps I do use are nothing too special just the regular games and chat services that almost any normal smartphone user has installed. The method I used to root was in a thread I found on this forum and on the first page of google. Well, my phone hasn't rebooted once when I was at my student room and has rebooted about 4 times this day when I am at my mom's. And I didn't receive another phone yet. This is still the phone I bought originally from Mediamarkt in Antwerp.
Niurez said:
Well it started before I rooted the phone. The apps I do use are nothing too special just the regular games and chat services that almost any normal smartphone user has installed. The method I used to root was in a thread I found on this forum and on the first page of google. Well, my phone hasn't rebooted once when I was at my student room and has rebooted about 4 times this day when I am at my mom's. And I didn't receive another phone yet. This is still the phone I bought originally from Mediamarkt in Antwerp.
Click to expand...
Click to collapse
I edited my previous post and may have a solution, try and load a different kernel since you are rooted.
mistahseller said:
I edited my previous post and may have a solution, try and load a different kernel since you are rooted.
Click to expand...
Click to collapse
Also the reboots happen when the phone is idle. It happened like two or three times the phone froze while using Google All Access and just rebooted. I am pretty sure the reboots aren't because of my faulty usage.
I will try the different kernel but I still feel not pretty comfortable that the original kernel just reboots. Maybe RMA is my only solution? Thing is the employee from Mediamarkt said I'd miss my phone for minimum three weeks. I don't even own my phone that long.
kernel panic is because of a different error. it can be caused by just about anything. in the partial last_kmsg that you posted, you didnt include the error, only the outcome of the error. chances are that its an app causing it though. yes, apps cause random reboots. there are too many that arent written very well. i suggest wiping your device and not adding any apps for a day. if you dont get any random reboots, add one app at a time until your phone starts rebooting. then youll know which app it is and isnt.
simms22 said:
kernel panic is because of a different error. it can be caused by just about anything. in the partial last_kmsg that you posted, you didny include the error, only the outcome of the error. chances are that its an app causing it though. yes, apps cause random reboots. there are too many that arent written very well. i suggest wiping your device and not adding any apps for a day. if you dont get any random reboots, add one app at a time until your phone starts rebooting. then youll know which app it is and isnt.
Click to expand...
Click to collapse
This is the last zip file syslog provided me. Hope it has more information.
Niurez said:
This is the last zip file syslog provided me. Hope it has more information.
Click to expand...
Click to collapse
looks ike an i/o error. it had trouble transferring data to a sector. i dont know what would have caused it. an app issue, a corrupted sector, whatever it was the phone doesnt like it.
id try running the phone without any installed apps for a day, see if it still reboots. if it doesnt, it was an app. if it still reboots, id wipe out the phone completely and flash the factory image. its also possible that a sector is corrupted somehow, or the data in it. a flash of the factory image should take care of it.
[ 2591.685522] mmc1: data txfr (0x00100000) error: -110 after 671 ms
[ 2591.685634] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 2591.685674] sdhci: Sys addr: 0x80000008 | Version: 0x00003802
[ 2591.685745] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 2591.685785] sdhci: Argument: 0x003ea888 | Trn mode: 0x0000002b
[ 2591.685857] sdhci: Present: 0x01e80100 | Host ctl: 0x00000035
[ 2591.685897] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
[ 2591.685967] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 2591.686006] sdhci: Timeout: 0x0000000c | Int stat: 0x00000000
[ 2591.686077] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[ 2591.686116] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 2591.686186] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008007
[ 2591.686257] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 2591.686296] sdhci: Resp 1: 0x00000000 | Resp 0: 0x00000900
[ 2591.686367] sdhci: Resp 3: 0x00000900 | Resp 2: 0x00000000
[ 2591.686406] sdhci: Host ctl2: 0x00000003
[ 2591.686445] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x35a40008
[ 2591.686517] mmc1: clk: 200000000 clk-gated: 0 claimer: mmcqd/1 pwr: 10
[ 2591.686557] mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[ 2591.686629] sdhci: ===========================================
[ 2591.690787] mmcblk0: error -110 transferring data, sector 4106376, nr 8, cmd response 0x900, card status 0x100c02
[ 2591.690868] end_request: I/O error, dev mmcblk0, sector 4106376
[ 2591.690912] end_request: I/O error, dev mmcblk0, sector 4106376
[ 2591.691009] Aborting journal on device mmcblk0p28-8.
[ 2591.691995] journal commit I/O error
[ 2591.692242] done.
[ 2591.705472] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2591.707353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2591.708900] Suspending console(s) (use no_console_suspend to debug)
[ 2591.785532] PM: suspend of devices complete after 74.713 msecs
[ 2591.786542] PM: late suspend of devices complete after 1.004 msecs
[ 2591.787851] PM: noirq suspend of devices complete after 1.302 msecs
[ 2591.788063] Disabling non-boot CPUs ...
[ 2591.788159] msm_pm_enter
[ 2591.788159] msm_pm_enter: power collapse
[ 2591.788159] msm_pm_enter: return
[ 2591.789882] PM: noirq resume of devices complete after 1.097 msecs
[ 2591.791208] PM: early resume of devices complete after 0.800 msecs
[ 2591.867621] PM: resume of devices complete after 76.407 msecs
[ 2591.869839] Restarting tasks ... done.
[ 2591.875706] EXT4-fs error (device mmcblk0p28): ext4_journal_start_sb:328: Detected aborted journal
[ 2591.875851] EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[ 2591.876665] Kernel panic - not syncing: EXT4-fs panic from previous error
Click to expand...
Click to collapse
simms22 said:
looks ike an i/o error. it had trouble transferring data to a sector. i dont know what would have caused it. an app issue, a corrupted sector, whatever it was the phone doesnt like it.
id try running the phone without any installed apps for a day, see if it still reboots. if it doesnt, it was an app. if it still reboots, id wipe out the phone completely and flash the factory image. its also possible that a sector is corrupted somehow, or the data in it. a flash of the factory image should take care of it.
Click to expand...
Click to collapse
Thanks, the thing is though that it rebooted three times while laying on my nightstand this day, every time I checked to see what time it was it was on the sim lock screen. Now during the day with average use (only using whatsapp and all access) it hasn't rebooted a single time. If there was a way to ensure a reboot I seriously don't know how to. If a flash of the factory image would be the final step, it may be in my best interest to start with that immediately instead of trying one day without apps? As I sometimes don't register a single reboot in four days.
Niurez said:
Thanks, the thing is though that it rebooted three times while laying on my nightstand this day, every time I checked to see what time it was it was on the sim lock screen. Now during the day with average use (only using whatsapp and all access) it hasn't rebooted a single time. If there was a way to ensure a reboot I seriously don't know how to. If a flash of the factory image would be the final step, it may be in my best interest to start with that immediately instead of trying one day without apps? As I sometimes don't register a single reboot in four days.
Click to expand...
Click to collapse
i think a day without apps first would be best, at least it would tell us if it is an app or not. one time on my gnex, i started getting random reboots when there were none before. about 3 days worth of reboots had me confused. i was about to flash the factory img, but i remembered i installed an app the day before the reboots started. even though i only opened it one time since i installed it, i decided to try removing it first. so i removed it, and never had a random reboot on my gnex since.
simms22 said:
i think a day without apps first would be best, at least it would tell us if it is an app or not. one time on my gnex, i started getting random reboots when there were none before. about 3 days worth of reboots had me confused. i was about to flash the factory img, but i remembered i installed an app the day before the reboots started. even though i only opened it one time since i installed it, i decided to try removing it first. so i removed it, and never had a random reboot on my gnex since.
Click to expand...
Click to collapse
Oh ok, I'll try this as soon as I'm done with my finals monday since I still use whatsapp quite a lot to discuss studying material. I also only got like 5 apps. The only apps that aren't recognized worldwide might be "De Lijn" app, which I use to check the bus times and "MyMobistar" to check information about my provider. Could this also be because something is faulty in my phone itself and that the only resolution would be to RMA it?
Niurez said:
Oh ok, I'll try this as soon as I'm done with my finals monday since I still use whatsapp quite a lot to discuss studying material. I also only got like 5 apps. The only apps that aren't recognized worldwide might be "De Lijn" app, which I use to check the bus times and "MyMobistar" to check information about my provider. Could this also be because something is faulty in my phone itself and that the only resolution would be to RMA it?
Click to expand...
Click to collapse
its possible. if it still happens after flashing the factory img, and some time without any apps installed, then id say the phones hardware is faulty, and rma it.
simms22 said:
its possible. if it still happens after flashing the factory img, and some time without any apps installed, then id say the phones hardware is faulty, and rma it.
Click to expand...
Click to collapse
Ok, I'll keep you updated.
Much thanks.
Niurez said:
Ok, I'll keep you updated.
Much thanks.
Click to expand...
Click to collapse
Hi! I'm facing same problem as you: random reboots when not using the phone.
Even my bugreport shows something similar to yours.
Did you resolve it?
Code:
[I]DISCLAIMER[/I]
All information and files — both in source and compiled form — are provided on an as is basis. No guarantees or warranties are given or implied. The user assumes all risks of any damages that may occur, including but not limited to loss of data, damages to hardware, or loss of business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty covering your device, it should be assumed that any warranty accompanying your device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 14.1 for the ZTE Blade S6 aka P839f30.
This is a beta release, so just some basic functions will be given.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
ril: calls, sms, data.
wifi: good.
sensors
gps
sound: clear and loud.
camera: rear and front.
torch
headphone detection
flash is working in new test builds.
not working:
We have to test to find more.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps.
optional: install your favourite kernel tool and set the cpu governor to interactive for example - do not use performance it will drain your battery, while you are using your device - not for the new test builds.
Click to expand...
Click to collapse
Changelog:
11.10.2018 - test build:
update los sources, security patch level 05.09.
04.03.2018:
make flashlight work.
integrate headphone detection.
update los sources, security patch level 05.02.
14.06.2018 - test build:
flashlight works also in stock camera.
governor are set by the system, no need to set them.
cores are managed by the system, shuting down and launching them one by one. This should save energy.
back and menu button can be toggled in the settings -> additional buttons.
Using stock venus files, video recording is working also hd playback should be fine.
Update sensor hub firmware to version 2.8.
update los sources, security patch level 05.06.
13.02.2018:
rebasing lots of things like kernel and device tree and using different vendor blobs.
Thus wifi signal is great and the microphone is better.
update los sources, security patch level 05.01.
22.11.2017:
reboot to recovery, download mode and power off should work fine now.
update los sources, security patch level 06.11.
19.10.2017:
device reboot fixed, no reboot if the device attempts to suspend.
wifi signal strength is better now.
5GHz wifi support is activated - to be tested.
remove nfc things.
Click to expand...
Click to collapse
Downloads
test build - 11.10.2018:
Google Drive
beta version - 04.03.2018:
Google Drive
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
XDA:DevDB Information
Unofficial LineageOS 14.1 [NJH47F] P839F30, ROM for all devices (see above for details)
Contributors
lightwars
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS 14.1
Version Information
Status: Beta
Current Beta Version: NJH47F
Beta Release Date: 2018-10-11
Created 2017-09-21
Last Updated 2018-10-11
Awesome, lightwars. Thank you for this Rom and the work you put into it.
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Apart from that everything it working great. The phone feels way faster than in stock Rom, videos play smoothly in 720p, 3d performance seemed ok (only tried Google earth, that was way better than in stock rom).
Only issue preventing me from using the phone are the reboots.
Again thank you very much for your great work. Please let me know, if I can help with anything.
xris99 said:
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Click to expand...
Click to collapse
It's good to hear, that this rom also work for the EU variant. Before,we have used different kernels...
Sadly I had discovered the reboots also. Thanks for doing some more testing.:good:
Will get some logs to see,if we could do something easily about it. Thought that it coul be related to just some kernel config mismatches, but it don't have to...
NFC is just left over from the starting point... It will be removed, but a little bit curious, that some variants have NFC support activated in the kernel config...
Out of curiousity, have you checked the GPS.conf? I've always had trouble with GPS on this phone but have got it mostly working after lots of fiddling, so I could post if that would be helpful.
xris99 said:
Awesome, lightwars. Thank you for this Rom and the work you put into it.
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Apart from that everything it working great. The phone feels way faster than in stock Rom, videos play smoothly in 720p, 3d performance seemed ok (only tried Google earth, that was way better than in stock rom).
Only issue preventing me from using the phone are the reboots.
Again thank you very much for your great work. Please let me know, if I can help with anything.
Click to expand...
Click to collapse
Willing you on for success with this.
I have an EU model which I'd like to install this on once it's functional enough (my regular daily phone).
I also have an old AS model that I may be able to revive for testing purposes (backlight failing intermittently after I dropped it, possibly a loose connection).
Thank you for trying lightwars. You are the only one who work for zte blade s6. I hope you build a stable version soon.
; Wow, many thanks @lightwars !!!
Hopefully soon you'll be have a stable on, that's my hope from ID version...
Regards,
Killermonk
Ok guys i want to install this rom but i cant. I cant find a tutorial here how to root the device. I try to install the recovery [RECOVERY][p839f30 / ZTE Blade S6] UNOFFICIAL TWRP [3.1.0-0] first but i failed too. There is a full guide how to do this? And if I install this there is a way back to the stock rom. Thanks.
@lagos911, rooting is easy. Just use Mobilego like in this video https://www.youtube.com/watch?v=dPDbAdm7B1c
Installing recovery isn't hard either. http://konstakang.com/devices/blades6/TWRP/
It is possible that the adress of the sdcard is different. (For example: sdcard0 in stead of sdcard), use the correct adress.
i install the rom at my phone (eu version) I get black screen after the install for 3 minites and then the device is shuting down.
What I do wrong? I wipe the device and I install the rom from my external sdcard.
lagos911 said:
i install the rom at my phone (eu version) I get black screen after the install for 3 minites and then the device is shuting down.
What I do wrong? I wipe the device and I install the rom from my external sdcard.
Click to expand...
Click to collapse
After installing the rom and you push reboot system, if the black screen (download mode probably) appears, hold the power button until the phone vibrates and reboots.
Now the ZTE splash screen should come up and the phone should boot hopefully.
lightwars said:
After installing the rom and you push reboot system, if the black screen (download mode probably) appears, hold the power button until the phone vibrates and reboots.
Now the ZTE splash screen should come up and the phone should boot hopefully.
Click to expand...
Click to collapse
Yes I do that some times from the second time and after because i didnt want to wait. But black screen continues to appear.
I rewipe (all king of wipes) and reinstall the rom 5 times but nothing happend.
I install the old rom because i was needed the phone. Phone start to loop reboot when I found out the bootfix and now its OK.
Maybe I try lineageOS 14.1 again at the weekend.
So I try to install the rom yesterday. I keep get the black screen after the I reboot the phone. This time I install the fix boot EU from the cyanogen rom. I reboot the phone and I saw the animation boot logo. I think I did it but the animation never go away. I let the phone for 30 minites but i never saw the menu of the new android.
lagos911 said:
So I try to install the rom yesterday. I keep get the black screen after the I reboot the phone. This time I install the fix boot EU from the cyanogen rom. I reboot the phone and I saw the animation boot logo. I think I did it but the animation never go away. I let the phone for 30 minites but i never saw the menu of the new android.
Click to expand...
Click to collapse
Ok, so we've got some problems with EU devices... maybe there are more variants, I'm think of EU, DE, UK, ES, PT and who knows... Could be small differences have an impact here...
To say it clearly to install the boot EU fix from the CM-12.1 thread has installed an other boot image for your phone which have kernel which will not work with nougat.
But anyway I believe I know why the device reboots itself, cause it can't suspend itself in the right manner. Let me show you a kernel log, how it should be:
Code:
<6>[ 189.766084] PM: suspend entry 2017-10-13 04:49:15.725432575 UTC
<6>[ 189.767479] mmc1: Starting deferred resume
<6>[ 189.767983] mmc0: Starting deferred resume
<6>[ 189.861591] mmc0: Deferred resume completed
<6>[ 189.907006] mmc1: Deferred resume completed
<6>[ 189.766118] PM: Syncing filesystems ... done.
<3>[ 189.999154] Error: returning -512 value
<6>[ 189.998043] Freezing user space processes ... (elapsed 0.008 seconds) done.
<6>[ 190.006568] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
<6>[ 190.011790] Suspending console(s) (use no_console_suspend to debug)
<6>[ 190.018262] [AK4375] ak4375_suspend(1402)
<6>[ 190.025845] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025845]
<6>[ 190.025892] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025892]
<7>[ 190.034218] --CWMCU--CWMCU_suspend
<6>[ 190.046580] PM: suspend of devices complete after 33.038 msecs
<6>[ 190.048343] PM: late suspend of devices complete after 1.737 msecs
<6>[ 190.053764] PM: noirq suspend of devices complete after 5.409 msecs
<6>[ 190.053774] Disabling non-boot CPUs ...
<6>[ 190.081114] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
...
<6>[ 400.663545] Enabling non-boot CPUs ...
<6>[ 400.664692] CPU1 is up
<6>[ 400.665735] CPU2 is up
<6>[ 400.666779] CPU3 is up
<6>[ 400.668230] CPU4 is up
<6>[ 400.669120] CPU5 is up
<6>[ 400.670027] CPU6 is up
<6>[ 400.670974] CPU7 is up
<6>[ 400.671561] PM: noirq resume of devices complete after 0.570 msecs
<6>[ 400.672983] PM: early resume of devices complete after 0.796 msecs
<7>[ 400.679137] --CWMCU--CWMCU_resume
<6>[ 400.689515] PM: resume of devices complete after 16.510 msecs
<6>[ 400.690769] runin_work:BatteryTestStatus_enable = 0 chip->usb_present = 0
<6>[ 400.690573] Restarting tasks ... done.
<6>[ 400.696613] PM: suspend exit 2017-10-13 05:59:11.279104088 UTC
But at the moment the device hangs up while trying to freeze the user space processes and fails.
I found that there is a problem with the device tree image of the kernel, so using the stock one everything is well.
I will make changes and a new version will appear soon.
In the meantime please try out flashing this bootimages after installing LOS-14.1:
Boot - LOS-14.1 standard image(AS)
Boot EU -LOS-14.1
Hopefully one of these works and the reboot issue shouldn't happen also.
lightwars said:
Ok, so we've got some problems with EU devices... maybe there are more variants, I'm think of EU, DE, UK, ES, PT and who knows... Could be small differences have an impact here...
To say it clearly to install the boot EU fix from the CM-12.1 thread has installed an other boot image for your phone which have kernel which will not work with nougat.
But anyway I believe I know why the device reboots itself, cause it can't suspend itself in the right manner. Let me show you a kernel log, how it should be:
Code:
<6>[ 189.766084] PM: suspend entry 2017-10-13 04:49:15.725432575 UTC
<6>[ 189.767479] mmc1: Starting deferred resume
<6>[ 189.767983] mmc0: Starting deferred resume
<6>[ 189.861591] mmc0: Deferred resume completed
<6>[ 189.907006] mmc1: Deferred resume completed
<6>[ 189.766118] PM: Syncing filesystems ... done.
<3>[ 189.999154] Error: returning -512 value
<6>[ 189.998043] Freezing user space processes ... (elapsed 0.008 seconds) done.
<6>[ 190.006568] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
<6>[ 190.011790] Suspending console(s) (use no_console_suspend to debug)
<6>[ 190.018262] [AK4375] ak4375_suspend(1402)
<6>[ 190.025845] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025845]
<6>[ 190.025892] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025892]
<7>[ 190.034218] --CWMCU--CWMCU_suspend
<6>[ 190.046580] PM: suspend of devices complete after 33.038 msecs
<6>[ 190.048343] PM: late suspend of devices complete after 1.737 msecs
<6>[ 190.053764] PM: noirq suspend of devices complete after 5.409 msecs
<6>[ 190.053774] Disabling non-boot CPUs ...
<6>[ 190.081114] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
...
<6>[ 400.663545] Enabling non-boot CPUs ...
<6>[ 400.664692] CPU1 is up
<6>[ 400.665735] CPU2 is up
<6>[ 400.666779] CPU3 is up
<6>[ 400.668230] CPU4 is up
<6>[ 400.669120] CPU5 is up
<6>[ 400.670027] CPU6 is up
<6>[ 400.670974] CPU7 is up
<6>[ 400.671561] PM: noirq resume of devices complete after 0.570 msecs
<6>[ 400.672983] PM: early resume of devices complete after 0.796 msecs
<7>[ 400.679137] --CWMCU--CWMCU_resume
<6>[ 400.689515] PM: resume of devices complete after 16.510 msecs
<6>[ 400.690769] runin_work:BatteryTestStatus_enable = 0 chip->usb_present = 0
<6>[ 400.690573] Restarting tasks ... done.
<6>[ 400.696613] PM: suspend exit 2017-10-13 05:59:11.279104088 UTC
But at the moment the device hangs up while trying to freeze the user space processes and fails.
I found that there is a problem with the device tree image of the kernel, so using the stock one everything is well.
I will make changes and a new version will appear soon.
In the meantime please try out flashing this bootimages after installing LOS-14.1:
Boot - LOS-14.1 standard image(AS)
Boot EU -LOS-14.1
Hopefully one of these works and the reboot issue shouldn't happen also.
Click to expand...
Click to collapse
I try to install the boot but file is corrupted
lagos911 said:
I try to install the boot but file is corrupted
Click to expand...
Click to collapse
I downloaded both files and they install just fine.
You have to switch from ZIP installing to image installing at the install dialog from twrp the button at the bottom right.
lightwars said:
I downloaded both files and they install just fine.
You have to switch from ZIP installing to image installing at the install dialog from twrp the button at the bottom right.
Click to expand...
Click to collapse
Yea i didnt know that with the image flashing. Thanks.
Actually I did it and I install the rom with your boot EU fix. No big diffrents at the interface from the 12.1 cm.
I dont working a lot with lineageOS but many thinks dont work. I enable wifi and disable automatic. Flashlight and some other thinks.
I hope you build a stable rom.
P.S. Now i have install the CM12.1 and when I try to enter the bootloader the device stuck.
Also I try to delete some system apps with ES explorer PRO and I get that my device its not rooted.
I have done something wrong with the rooting?
lagos911 said:
P.S. Now i have install the CM12.1 and when I try to enter the bootloader the device stuck.
Also I try to delete some system apps with ES explorer PRO and I get that my device its not rooted.
I have done something wrong with the rooting?
Click to expand...
Click to collapse
I am not sure I can follow your description... What means stuck? bootloader displays just a black screen.
Normally you can activate root in the developer settings, which are displayed after clicking serveral times on the build number. There you will find an option to enable/disable root for apps and adb.
Or if you prefer other tools like supersu install it first, then try again.
Remember to ask question for CM12.1 inside the appropriate thread.
Sorry for the wrong topic. I didint know that the bootloader appearing a black screen. Usually they have a menu.
I forgot to mention that the option for root explorer at ES explorer PRO you can activated from here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help :/
I've installed this onto my zte blade s6 but my internet doesn't turn on on the phone and I flashed the eu fix by lightwars on my recovery so now i don't have a recovery and my phone isn't rooted. PLEASE HELP.
I have put together quick guide to unbricking the 8th gen Fire HD8 (karnak) stuck on the white Amazon logo, without having to take the back off or having to short any wires. I hope this will help someone out if they are stuck on what to do next. This is based on other great posts by By k4y0z & xyz & Xinto & Scripts used amonet-karnak-v3.0.1.zip and brick-karnak.zip
I am assuming that you are already using a Linux installation or live-system running ADB and have the amonet-karnak-v3.0.1.zip and brick-karnak.zip extracted to have bricked your tablet in the first place I am basically a total newbie but I have now tried this 3 times on 2 8th gen Fire HD8's (karnak) tablets with differing Firmware that were stuck on the boot logo. Please note I am not responsible of any physical damage in your tablet, if you choose to make these modifications.
1. First power off the tablet (Hold power button down for 20 seconds until the Amazon logo disappears)
2. Hold down the left Volume button, while pressing the Power on button. Then Plug the tablet back in.
3. From inside the brick-karnak/amonet folder open a new terminal and TYPE
Code:
sudo ./brick.sh
The terminal will say ...Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
4. Make sure you type YES, not just y or yes like I made the mistake of doing a few times!
The terminal will then say
Bricking PL Header
Check instructions on device
target reported max download size of 114294784 bytes
Sending 'brick' (111957 KB)...
OKAY [ 3.886s]
Writing 'brick'...
On the Amazon Fire screen it will display.... All good now unplug and power off the device.
5. Unplug the tablet and power it off (Hold power button down for 20 seconds)
6. From inside the amonet-karnak-v3.0.1/amonet open a new terminal and TYPE
Code:
sudo ./bootrom-step.sh
The terminal will say .... Waiting for bootrom
7. Plug the tablet back in and the Terminal will say something like
found port = /dev/ttyACM0
[2019-12-26 21:09:53.550179] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
8. Press the Enter Key
The Terminal will say something like
[2019-12-26 21:10:00.564737] Init crypto engine
[2019-12-26 21:10:00.580769] Disable caches
[2019-12-26 21:10:00.581253] Disable bootrom range checks
[2019-12-26 21:10:00.622439] Load payload from ../brom-payload/build/payload.bin = 0x4888 bytes
[2019-12-26 21:10:00.626302] Send payload
[2019-12-26 21:10:01.261823] Let's rock
etc, etc, until.....
[2019-12-26 21:12:56.277773] Reboot
9. Unplug the tablet again
10. From inside the amonet-karnak-v3.0.1/amonet folder open a new terminal and TYPE
Code:
sudo ./fastboot-step.sh
The Terminal will say < waiting for any device >
11. Plug the tablet back in
The Terminal will say something like target reported max download size of 114294784 bytes
sending 'recovery' (13604 KB)...
OKAY [ 0.474s]
writing 'recovery'...
OKAY [ 0.619s]
finished. total time: 1.093s
target reported max download size of 114294784 bytes
sending 'MISC' (0 KB)...
OKAY [ 0.012s]
writing 'MISC'...
OKAY [ 0.006s]
finished. total time: 0.018s
rebooting...
finished. total time: 0.052s
Your device will now reboot into TWRP.
Now your tablet will now reboot back into TWRP recovery ready for action.
I have an 8th gen fire HD. I tried the root method and I can complete all steps up to the reboot into recovery after "sudo ./bootrom-step.sh". When the tablet reboots, the amazon logo appears briefly and I can see text that says recovery but then the screen goes black. I have tried the power button, but that does not wake up the screen and I cannot complete the root. Any suggestions?
Jik Sey, THANK YOU!
your topic saved my tablet, i was almost
throwing it away
basically i have installed a bad magisk module , got bootloop and when i tried to remove in twrp, losted the recovery acess
following this steps, the problem was solved!
hudsonbra said:
Jik Sey, THANK YOU!
your topic saved my tablet, i was almost
throwing it away
basically i have installed a bad magisk module , got bootloop and when i tried to remove in twrp, losted the recovery acess
following this steps, the problem was solved!
Click to expand...
Click to collapse
Thanks for the feedback. I was in exactly the same situation and was just about to give up on my tablet as well
draco2020 said:
I have an 8th gen fire HD. I tried the root method and I can complete all steps up to the reboot into recovery after "sudo ./bootrom-step.sh". When the tablet reboots, the amazon logo appears briefly and I can see text that says recovery but then the screen goes black. I have tried the power button, but that does not wake up the screen and I cannot complete the root. Any suggestions?
Click to expand...
Click to collapse
Sorry I have only just seen your post. Hopefully you have sorted the problem now. It could be that your tablet is not fully powered down properly, only sleeping, unplug the tablet and power it off, Hold power button down for 20 seconds before typing the sudo ./bootrom-step.sh part.
Would this work on 2017 Douglas?
I understand these are different "brick" files created to exploit different things on the Karnak vs. Douglas models, but in theory could this work if I used the brick files from the Douglas thread to unbrick my Douglas? My 2017 is stuck on the amazon logo as well and is non-responsive. I'm tempted to try these same instructions to see what happens.
bentley4me said:
I understand these are different "brick" files created to exploit different things on the Karnak vs. Douglas models, but in theory could this work if I used the brick files from the Douglas thread to unbrick my Douglas? My 2017 is stuck on the amazon logo as well and is non-responsive. I'm tempted to try these same instructions to see what happens.
Click to expand...
Click to collapse
I don't know which versions of Fire OS the brick script for Douglas will work on, but you can always open the case and use the shorting method to enter bootrom mode if you have to. Amonet for Douglas also has 'bootrom-step.sh' and 'fastboot-step.sh' scripts. Run those two after getting into bootrom mode and it should install TWRP on your device: possibly wiping the internal storage in the process. You will then probably have to install Fire OS (change the filename from '.bin' to '.zip') or a custom rom to boot the device up.
MontysEvilTwin said:
I don't know which versions of Fire OS the brick script for Douglas will work on, but you can always open the case and use the shorting method to enter bootrom mode if you have to. Amonet for Douglas also has 'bootrom-step.sh' and 'fastboot-step.sh' scripts. Run those two after getting into bootrom mode and it should install TWRP on your device: possibly wiping the internal storage in the process. You will then probably have to install Fire OS (change the filename from '.bin' to '.zip') or a custom rom to boot the device up.
Click to expand...
Click to collapse
Thanks, I will look up how to do that. Wiping and installing Lineage was my entire reasoning for doing this, so I'm good with that end result.
Work for Fire stick tank?
Would this guide be applicable to my fire stick (tank) that got stuck on the amazon white logo since both use similar exploits?
Thank you! Instructions and process worked perfectly for my issue.
I am working on a bricked Fire HD 8 2018 device but am receiving errors during the GPT check. I can't find anywhere how to repair the GPT to proceed with restoring the device.
Wait for payload to come online...
All good
Check GPT
RuntimeError: What's wrong with your GPT?
It stops there...
I saw some gpt-fix scripts for the 2017 models but haven't seen anything for 2018. Any help greatly appreciated.
I am pretty much a newbie myself learning by trial and error. But the nearest answer I could find to your problem is https://forum.xda-developers.com/posts/83691939/
Worked perfectly. Thanks!
Помогите!
Не заходит в recovery,постоянно перезагружается