This is for people who know how to debug to troubleshoot and correct issues in the jf tree, or at least provide relevant info.
Every post in the discussion thread should include your build string and variant, or you will be ignored.
I am not supporting your end user needs, but you can take that to the Q&A thread.
rom: https://www.androidfilehost.com/?w=files&flid=13420
use this gapps: https://www.androidfilehost.com/?w=files&flid=21354
do not flash another kernel
do not bring kk /data
known jf issues:
some overlays disabled
double tap home = camera is not working
swype on google keyboard not working
kernel source: https://github.com/CyanogenMod/android_kernel_samsung_jf
since nightlies are enabled, this thread wont be watched/updated anymore.
thanks for helping with the bringup.
Alright alright alriiiiiiiiiiight
Up & running, have cell and sound. Maybe NFC not working. GPS is, WiFi is. Thank you!
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
what filesystem is it using?
hoffreaper said:
ROM is not able to access the SD card in my phone. Only the internal storage of the device is available. WIFI, GPS, and LTE are all able to connect without a problem. Camera is also working without issue.
Click to expand...
Click to collapse
Exfat isn't working yet I believe, fat32 does tho
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
To the people who have this running What gapps are you using?
archangeles said:
How did you guys install it? I took a look inside the zip and found a lot of stuff missing, there's not even a build.prop, most of the bulk of the zip is on a file called system.new.dat
Click to expand...
Click to collapse
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
dcd1182 said:
For testing...
Most stuff is working.
You tell me whats broken.
https://www.androidfilehost.com/?fid=95784891001613232
Click to expand...
Click to collapse
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
ShinySide said:
Gapps
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
---------- Post added at 05:40 PM ---------- Previous post was at 05:32 PM ----------
Did a test on making a call to my VM.while calling works ,trying to hang up it says hanging up but never does and VM lady just keeps talking til VM cuts off due to not entering anything
Click to expand...
Click to collapse
same here on 1st call, but 2nd+ call hung up fine. same for you?
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
I'm actually running twrp, do you recommend switch to cwm to install the zip?
I used CWM. No problems with 1st call for me, and good since
dcd1182 said:
same here on 1st call, but 2nd+ call hung up fine. same for you?
Click to expand...
Click to collapse
Na Tried 4 times, refuses to hang up. Acts like it hangs up visually but in call screen stays on saying hanging up and vm just keeps talking
archangeles said:
I'm actually running twrp, do you recommend switch to cwm to install the zip?
Click to expand...
Click to collapse
shouldnt matter
dcd1182 said:
install zip in cwm as always
https://source.android.com/devices/tech/security/dm-verity.html#block-otas
Click to expand...
Click to collapse
dcd1182 said:
shouldnt matter
Click to expand...
Click to collapse
I get an error executing updater binaries in zip
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
try cwm then
i use philz 6.58.7, works here
edit: were not bringing back file based flashing, so if the recovery doesnt support block based, recovery needs updating
archangeles said:
I get an error executing updater binaries in zip
Click to expand...
Click to collapse
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
ShinySide said:
There's something wrong on your end then. I've flashed both builds with twrp 2.8.0.1 without issue
Click to expand...
Click to collapse
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
archangeles said:
I know there is, I had a similar problem updating to 4.4.4 from 4.4.2 tw custom rom, and fixing permissions seemed to fix that, but this time it does nothing, could the bootloader be a problem in any way? I'm still on 4.4.2 because 4.4.4 tw never installed properly, but pac-man 4.4.4 worked just fine. Any pointers?
Click to expand...
Click to collapse
not bootloader
try to format system
Related
[UPDATE]
Transparent bars were added to stock KitKat in the 4.4.1 update, this mod is no longer necessary unless you haven't updated to 4.4.1 or above
Credit to @bokagavrilov for modding the files and to @genocide_ru for providing the stock deb file
Flash the modded zip files in recovery, wipe cache, fix permissions and reboot.
If you experience a bootloop, boot back into recovery and flash the stock zips provided.
KRT16O
flo [Wi-Fi version]:
Transparent: https://www.dropbox.com/s/xkks0al1lu0cu6z/transparent.zip
Stock: https://www.dropbox.com/s/zcxba8dny1u6r4z/stock.zip
deb [LTE version]:
Transparent: https://www.dropbox.com/s/kebn56qkrc06pcw/transparentn7deb.zip
Stock: https://www.dropbox.com/s/97uolklhcw1g9ve/stockn7deb.zip
KRT16S
flo [Wi-Fi version]:
Transparent: http://goo.gl/vvQUDV
Stock: http://goo.gl/DHZbXx
deb [LTE version]:
Transparent: http://goo.gl/0s9qSp
Stock: http://goo.gl/ZmkDES
Did you test to see if that zip would work with N7? Sometimes that stuff is interchangeable.
runderekrun said:
Did you test to see if that zip would work with N7? Sometimes that stuff is interchangeable.
Click to expand...
Click to collapse
Doesn't work, getting bootloops.
I'd like to see this too.
i have just made them they are just for stock image (you can test on others but they might not work)
transparent:https://www.dropbox.com/s/xkks0al1lu0cu6z/transparent.zip
and stock in case u end up bootlooping: https://www.dropbox.com/s/zcxba8dny1u6r4z/stock.zip
bokagavrilov said:
i have just made them they are just for stock image (you can test on others but they might not work)
transparent:https://www.dropbox.com/s/xkks0al1lu0cu6z/transparent.zip
and stock in case u end up bootlooping: https://www.dropbox.com/s/zcxba8dny1u6r4z/stock.zip
Click to expand...
Click to collapse
Thank you so much! OP updated
bokagavrilov said:
i have just made them they are just for stock image (you can test on others but they might not work)
transparent:https://www.dropbox.com/s/xkks0al1lu0cu6z/transparent.zip
and stock in case u end up bootlooping: https://www.dropbox.com/s/zcxba8dny1u6r4z/stock.zip
Click to expand...
Click to collapse
Scratch that, after flashing it I'm getting a boot loop. Are you on the Wi-Fi or LTE version? I'm on the Wi-Fi one and I noticed your stock framework-res.apk is ~8MB whereas my one is ~14MB, any idea what might have gone wrong?
AlderCass said:
Scratch that, after flashing it I'm getting a boot loop. Are you on the Wi-Fi or LTE version? I'm on the Wi-Fi one and I noticed your stock framework-res.apk is ~8MB whereas my one is ~14MB, any idea what might have gone wrong?
Click to expand...
Click to collapse
ehm im on the wifi too and i just reflashed them and everything is okey about the size when u zip a file it gets compressed thats why its 8mb (and you should flash it in recovery not push it to /system/framework )
bokagavrilov said:
ehm im on the wifi too and i just reflashed them and everything is okey about the size when u zip a file it gets compressed thats why its 8mb (and you should flash it in recovery not push it to /system/framework )
Click to expand...
Click to collapse
You're right about the compression, when I looked inside the zip in Solid Explorer it said the .apk was ~8MB and I assumed that it was telling me the uncompressed size the same way the likes of WinZip would. I did flash in recovery when I got the bootloop but I'll try again.
AlderCass said:
You're right about the compression, when I looked inside the zip in Solid Explorer it said the .apk was ~8MB and I assumed that it was telling me the uncompressed size the same way the likes of WinZip would. I did flash in recovery when I got the bootloop but I'll try again.
Click to expand...
Click to collapse
It worked this time, only thing I did differently was wipe the cache this time, did think it was necessary but here we are :laugh:
AlderCass said:
Scratch that, after flashing it I'm getting a boot loop. Are you on the Wi-Fi or LTE version? I'm on the Wi-Fi one and I noticed your stock framework-res.apk is ~8MB whereas my one is ~14MB, any idea what might have gone wrong?
Click to expand...
Click to collapse
bad download maybe i just unziped the files on my pc and the framework its 15.2mb i also tried pushing it and it worked
bokagavrilov said:
bad download maybe i just unziped the files on my pc and the framework its 15.2mb i also tried pushing it and it worked
Click to expand...
Click to collapse
It worked this time, cache wipe was all it needed I think thanks again!
AlderCass said:
It worked this time, cache wipe was all it needed I think thanks again!
Click to expand...
Click to collapse
:good: :good:
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
can someone test it on the mobile version too ? ( make a backup before just in case) and if doesn't work feel free to post the framework-res.apk and i will modify it
Just bootloops on mine downloaded and flashed three times in TWRP also wiped cache each time.
woolmonkey said:
Just bootloops on mine downloaded and flashed three times in TWRP also wiped cache each time.
Click to expand...
Click to collapse
mobile version ?
bokagavrilov said:
mobile version ?
Click to expand...
Click to collapse
No WIFI
woolmonkey said:
No WIFI
Click to expand...
Click to collapse
make sure you are on stock factory image i just did it for my n4 too, must be something wrong on your end because its just a line of code that has to be changed. There is nothing that can go wrong there
I doubt this could have anything to do with it but are you guys on Dalvik or ART? I'm on ART myself
AlderCass said:
I doubt this could have anything to do with it but are you guys on Dalvik or ART? I'm on ART myself
Click to expand...
Click to collapse
Dalvik here ART its still too early for me
bokagavrilov said:
make sure you are on stock factory image i just did it for my n4 too, must be something wrong on your end because its just a line of code that has to be changed. There is nothing that can go wrong there
Click to expand...
Click to collapse
Completely stock flashed the system.img after each failed attempt of the boot loop. Also tried it as art same thing also flashed it with CWM instead of TWRP still the same loop. First it loads and I see the lock screen then it reboots and just stays in the pulsating circles.
TouchWiz-4.4 ROM FIXER for Developer Edition devices
WARNING: These files are for Developer Edition devices ONLY. Kernels cannot be flashed on the retail VZW Note 3 devices!
THIS PROCESS ALSO SETS KNOX 0x1
Own a DevEd? Flashed the firmware/modem bits to the new TW4.4 in hopes of seeing some of the improvements or running a stock-modded ROM?
FIRST: Big shout out to @Imoseyon who has a VERY nice kernel for unlocked devices here:
http://forum.xda-developers.com/showthread.php?t=2488082
Go over there and tell him thanks, because I had spent a day or so trying to fix up a boot.img but wasn't having much luck due to a crash in TIMA memory. But, then I read that someone had gotten the leak booted w/ Imoseyon's kernel and was able to rip it apart and pull just the absolute minimum changes to get a VERY close to stock kernel / ramdisk setup for the 4.4 leak.
WHAT IS THIS?
Several issues were noticed immediately on DevEd devices due to the fact that we can't flash certain portions of the updated ODIN files (aboot, sbls, etc):
Play Movies won't stream
External SD card won't mount
Lockscreen settings don't work
Imoseyon's kernel was the only boot.img which would run 4.4 leak due to aboot/devicetree changes and TIMA crashes
The files below fix these issues and provide a VERY close to stock boot.img for use on DevEd devices.
FIX FILES: 2 flashable .zip files (for use in recovery):
1st flash file: flash-vzw-de-4.4-kernel-v1.0.zip
This is a rebuilt boot.img containing:
New NC2 stock-based kernel with CONFIG_TIMA disabled
Rebuilt dt.img using 1st gen dtbTool for use with our 4.3 aboot
Ramdisk has default.prop changes for disabling TIMA, KNOX and securestorage (Credit: @Imoseyon / leanKernel 2.4 ramdisk)
This file only needs to be flashed once (as long as you don't swap to AOSP ROMs). You can also use leanKernel by @Imoseyon if you like his work. The difference between this kernel and his are: I used the identical settings as the stock NC2 kernel (Kernel modules are enabled, etc) in an attempt to eliminate as many differences between the DevEd and the retail device. His kernel has a TON of tweaks and updates. But, could in theory have issues running the stock NC2 VZW leak.
Kernel source: https://github.com/Hashcode/android_kernel_samsung_hlte/tree/hlteatt-kk-nc2
2nd flash.zip file: flash-tw44-sys-files-fixes-v1.0.zip
A set of system file changes which fix the issues noted above (this file should be flashed after EVERY TW-based ROM is flashed)
Downloads:
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
Instructions:
Download the above files and place them on your device's storage
Reboot into recovery
Flash flash-vzw-de-4.4-kernel-v1.0.zip if you need to fix kernel (coming from AOSP)
Flash flash-tw44-sys-files-fixes-v1.0.zip after ANY flash of TW-based 4.4 ROMs to fix system files
Reboot, no need to wipe cache, etc
XDA:DevDB Information
[DEVED/TW-ROM FIX] Developer Edition TW-4.4 ROM Fix Files, a Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
Hashcode
Version Information
Status: Beta
Stable Release Date: 2014-04-27
Created 2014-04-27
Last Updated 2014-04-27
Reserved
Nice!
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Great! Quick test results:
I can see my exFAT 64GB external SD card.
Cut and paste works with my password manager.
I still cannot set a screen lock PIN.
Sent from my SM-N900V DevEd using Tapatalk
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
Hi,
I don't post enough to reply to the thread in beans new dev edition kernel, but I wanted to let you and the other guys know about how I got the pin and password unlock to work for me.
I found it on a random xda thread:
In build.prop,
security.mdpp.result=None, changed to #security.mdpp.result=None
This let's you use the pin unlock as well as the other options that are currently greyed out.
This works for me with the deodex 4.4 rom and leankernel even before applying the fixes in beans new thread.
Please post this in the thread so other people will know.
Hope this helps.
Click to expand...
Click to collapse
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
DavidFlory said:
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
Click to expand...
Click to collapse
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
stargzrr11 said:
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
Click to expand...
Click to collapse
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Thepooch said:
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Click to expand...
Click to collapse
Thanks for the additional information.
I tried it again - I must have goofed up my build.prop somehow.
Regardless, it booted back up fine, but the swipe/pattern/pin lock options are still grayed out (just like the screenshot in the thread above). I tried wiping cache/dalvik without luck. Also tried re-applying Hashcode's sys-files-fixes zip - didn't make a difference.
I do see there is also a "security.mdpp" line in the build.prop a few lines above. Wonder if that needs commented out too.
---------- Post added at 11:39 AM ---------- Previous post was at 11:17 AM ----------
Thepooch said:
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Click to expand...
Click to collapse
Play movies is working for me...
If it's still busted for you, try going into "Application Manager", "All", find "Google Play services" and click "Uninstall updates". Once you uninstall it, Hangouts should immediately popup saying you need to update Google Play services. Re-apply this update. Try play movies again...
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
TSman74 said:
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
Click to expand...
Click to collapse
No firmware update in this. Just ROM and kernel.
As far as I know there isn't a flashable modem firmware for that yet.
Sent from my SM-N900V using Tapatalk
I should say for my device, I'm not 100% sure if I flashed @BeansTown106's ROOT/ROM or whether I flashed the leak's system.img.ext4 file via heimdall (I remember flashing SuperSU initially to get root tho).
And I literally have no extra mods installed other than these.
So, I'd like to keep track of who has the following working and what users are doing to fix their issues:
- SD card (seems like it's fixed for most)
- Play Movies (@ThePooch it's not working -- possibly need to remove the updates / re-install?)
- Lock screen settings (Seems like I'm still the only one with working settings :/ -- possibly need a build.prop fix)
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Thank you!
Hash,
I assume that we need to be on twrp 2.7 ( 4.3 edition).
Several people were complaining about the sd card not mounting -but fat32 wokrs.
here is a small donation 5W64555......
Thank you for keeping these devices up and running.
Hashcode said:
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Thepooch said:
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Click to expand...
Click to collapse
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Not a special edition, I'm debugging the retail version of Safestrap using the new leak setup.
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Dev Roms
Is there somewhere else we can put the Dev Roms and whatever else Dev there may be?
stargzrr11 said:
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Agreed. Are you using SS?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
I'm looking into it also thinking of the possibility of a special Odin package for the DE straight from the leak minus bootloader and plus Hashcode kernel so it will actually boot proper.
Hi everyone!
I'm using the latest MoKee MK44 ROM for our Ace.
I really like this ROM but there seems to be a problem with the kernel. It reboots randomly during read or write processes.
Does anybody know something to fix that problem?
I attached the last_kmsg, maybe you can tell me whats going wrong here.
EDIT: It seems that it's not MoKee causing this problem.
EDIT2: I got a solution for the problem, take look at this post.
I haven't experienced that....but if I were to,I would definitely just clean flash ROM again.
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Does really nobody knows something about the last_kmsg? Here are so many professionals and none of you can help?
Attached another last_kmsg, I took it right after a reboot.
Pulled battery, booted to recovery and copied it so I think there aren't many non-relevant events at the end of the file.
Attached file is now zip, maybe you don't like rar, I don't know. Thanks
Vega Bullet said:
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Click to expand...
Click to collapse
No reboots here
marknoll said:
No reboots here
Click to expand...
Click to collapse
:good:
Ok, tried clean flashing once again, still the same result.
So what about the last kmsg?
What recovery are you using?
marknoll said:
What recovery are you using?
Click to expand...
Click to collapse
TWRP 2.7.1.0
Used the latest 4ext before that but had some problems, so I changed to twrp which works better I think.
Use the mod twrp jriors... That flashes everything.
marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
So you think it's a flashing problem? Like I said, I think there were no problems (especially random reboots) with other ROMs, that's why I didn't thought it's a flashing problem. But I will try it again.
EDIT: Can you give a link? Would help me saving some time
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
marknoll said:
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
Click to expand...
Click to collapse
Well...
Vega Bullet said:
TWRP 2.7.1.0
Click to expand...
Click to collapse
I didn't know if "jriors" one is a special version but that is exactly the recovery I am using.
I got it from that thread, not from the mirror on page 4 you linked me to but from his first post.
So this would not change anything. Please correct me if I'm wrong.
All I can say is that maybe u got a bad download. Redownload the ROM and check md5. Then flash it with jriors. Should work fine then
Ok, looked for the checksums, matched.
And again, does really nobody know anything about the kernel log file? No idea? No clues?
I'm testing latest CM11 once again, maybe I find something...
EDIT: Tested under same conditions. Same problem with CM11. So I think an app or setting is causing it.
Would be very helpful if someone can take a look into kernel log.
My advice is to factory reset from recovery. Then go under advanced wipe and chose cache, dalvik,android secure and system wipe. Then flash the ROM and gapps..reboot after and let it run before logging in play store or installing any apps
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
[/COLO
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Can I plz have the link you're getting this ROM from? I think that maybe ur downloading an incompatible rom
I'm sure I do the procedures correct, tried simple factory reset (with recovery) and additionally wipe /system and android secure too.
Download ROM from here, look for checksums, flash boot.img separately.
But now, even if I only use it like it's been flashed, I'm getting reboots. Not only reboots. It seems that everything isn't correct.
Freshly flashed, want to reboot device normally but hangs during reboot dialog or bootloops...
Currently I'm testing the first ROM flashed the DHD with, CM11 OnePlusOne Edition and
THAT Rom seems to work. No reboots, hangs or bootloops, very confusing...
So it's getting very difficult to help me, no pattern I can follow to get out what's wrong
I thought Titanium Backup was the problem but like I said, even if it's clean it doesn't work.
Well, I will test everything again, let's see.
Are you s off?
marknoll said:
Are you s off?
Click to expand...
Click to collapse
No, thought of it but I was to lazy to read me through all the things I have to do,
flashing original ROM and what I have to keep in mind and so on...
Maybe I will try it but my time is also limited.
In the last_kmsg you can read that right after "rebooting in 5 seconds" there is "BUG: scheduling while atomic: htc_ebdlogd..."
I simply deleted the file htc_ebdlogd (because I don't know what else to do) and rebooted, seems to be no problem without that.
Till now the problem does not occurred. Till now..
Same problem on CM11 M9?
I think I'm having the same problem with CM11 on my Ace. I installed it this afternoon and have had random reboots on multiple occasions. Can't find a pattern for when it occurs. I don't have a logcat log from when it happens yet, but I'll try to obtain one.
My phone is S-ON (only HTCDev unlocked) and I used the TWRP 2.7.1.0 from [1], the CM11 M9 build from [2] and the PA GApps Modular Nano package from [3]. I installed by:
In TWRP:
1) Wipe (should wipe everything right?)
2) Install CM11 zip
3) Install PA GApps zip
Then flashed the extracted boot.img from fastboot.
I'd be very interested in hearning if deleting htc_ebdlogd really worked for you Vega Bullet.
Cheers,
Elvis
[1] http://forum.xda-developers.com/showthread.php?t=2780164
[2] http://forum.xda-developers.com/showthread.php?t=2533007
[3] http://forum.xda-developers.com/showthread.php?t=2397942
The kernel log is located under /proc named last_kmsg
For now it works fine let's but I don't really know if there are any consequences nor if it works.
EDIT: After a few days of testing a can say there are no reboots anymore, I am using MoKee MK44 for Ace and it's working fine.
Although I still don't know about consequences I can't say there are any but you do it without warranty.
So if you experience the same error
(means random reboot,
look into /proc/last_kmsg,
you should see the line "BUG: scheduling while atomic: htc_ebdlogd..."),
make a nandroid and delete htc_ebdlogd (should be located in /system/bin).
Btw, looking at the MoKee Source I only see one reference to this binary, it's located under ramdisk/init.spade.rc .
Maybe someone know's more and what it's good for, like I said without it I don't see differences...
Q&A for [ROM] [4.4.2] [TW] Pimpdroid 3.0 beta 20140930 {WiFi, 3G, and LTE!}
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Works perfectly!!
This is my first post since i registered here, and im very happy for the one who created pimpdroid 3.0!!
but i have a little question, how can i delete apps like google maps, music app and other "integrated" apps?
Somebody who knows?
Titanium backup is your friend.
Sent from my SM-T210 using XDA Free mobile app
2.5 version fine, new beta error
Thanks for this guy, got 2.5 working, but the 3.0.3 beta fails and says,
"set_metadata_recursive some changes failed"
error to it.
Using TWRP 2.6 from:
http://forum.xda-developers.com/showthread.php?t=2531784
Lord Sif said:
Thanks for this guy, got 2.5 working, but the 3.0.3 beta fails and says,
"set_metadata_recursive some changes failed"
error to it.
Using TWRP 2.6 from:
http://forum.xda-developers.com/showthread.php?t=2531784
Click to expand...
Click to collapse
Use one of @moonbutt74 's recoveries, as specified in OP.
Bootloop
Hello,
I have downloaded the Jellybean version of Pimpdroid for my Tab 3 10.1 and placed it in my SD card. However, when I flashed it through Philz recovery (I cleared the data, system, cache and Dalvik cache) I get stuck in a bootloop so I simply restore it from my backup. I then try again. Bootloop. I would like to know how to rectify this as I love the work done to this ROM.
Tonio2000 said:
Hello,
I have downloaded the Jellybean version of Pimpdroid for my Tab 3 10.1 and placed it in my SD card. However, when I flashed it through Philz recovery (I cleared the data, system, cache and Dalvik cache) I get stuck in a bootloop so I simply restore it from my backup. I then try again. Bootloop. I would like to know how to rectify this as I love the work done to this ROM.
Click to expand...
Click to collapse
Hey , try flashing the jellybean builds from angel666's TWRP
Aeyan Ashraf said:
Hey , try flashing the jellybean builds from angel666's TWRP
Click to expand...
Click to collapse
I tried doing that with a clean flash but now after i flashed it, my tab reboots and then reboots into recovery.
UPDATE: I managed to flash the rom by flashing the first build which worked and then dirty flashing the latest build over it.
I'm having problems with X multi-window. It's asking me whether I want to put the application on the left or right but only folks the entire screen. It never splits.
Any ideas?
dshulman said:
I'm having problems with X multi-window. It's asking me whether I want to put the application on the left or right but only folks the entire screen. It never splits.
Any ideas?
Click to expand...
Click to collapse
I'm having the same issue with beta3
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
Also, I have another question, how can I change the sound that run when I touch the screen, actually it plays the camera sound but it's sooo anoying, how to redtore the stock sound?
igos2 said:
I'm having the same issue with beta3
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
Also, I have another question, how can I change the sound that run when I touch the screen, actually it plays the camera sound but it's sooo anoying, how to redtore the stock sound?
Click to expand...
Click to collapse
Go into Settings... Sound and you'll see the setting to turn off Touch Sounds. I hate that as well.
Il turned it off 5 minutes after I installed this rom, but I want it to be on with a less annoying sound.
igos2 said:
Il turned it off 5 minutes after I installed this rom, but I want it to be on with a less annoying sound.
Click to expand...
Click to collapse
So go into sound and go to volume set system volume to a bit low .....................
I want to change the sound, stop saying OOT things
igos2 said:
I want to change the sound, stop saying OOT things
Click to expand...
Click to collapse
I can tell u the method but I think you'll find it very difficult to do it.....
If u want that method write it up here.....
Sur, I think it must be a .wav file somewhere, I can copy the stock sound it place of that .wav, just need to know the path of each of this files.
Helo,
i have bevor Pimpdroid installed have the Bindroid. After installing Pimpdroid i have 2x Bootloop and than going into Recovery.
I have do all right.
But the problem is, i cant install Stock or another ROM after the experience with Pimpdroid. I can do what i want, i get ever 2x Bootloop an the P5210 (wifi) going into Recoverymode.
I tryed another Recovery, have now TRWT installed, but its no better... ok this recovery is 1000x better than CWM, but not for my problem.
So i have try all and now i search the way to install the "stock recovery" or another way the rom install with odin, how i make from zip an tar.md5 file? I see by another user the have the stock rom in tar.md5 and i found only stockrom in zip format?
PS: I havent installed the Beta4, because the developer writed that is not work, i have installed beta3 and after that not worket i have try beta 2,1 and the old 2.5 an than every stock rom than i got.
igos2 said:
Sur, I think it must be a .wav file somewhere, I can copy the stock sound it place of that .wav, just need to know the path of each of this files.
Click to expand...
Click to collapse
Hello brother ,
The file is in system/media/'here' and and it is in .ogg format ......the name of the file I forgot .... I will tell u in some time
Sent from my GT-I9082 using XDA Free mobile app
I have found it on system/media/ui, the file is TW_Touch.ogg.
Status 7
I've done some Google-fu and I still can't figure this one out.
I've done everything I can tell correctly, cleared everything, rooted, put the ROM on my root. I boot into Philz, go into install zip, start the installation and it goes through "installing update". After a short while a message pops up saying "set_metadata_recursive: some changes failed" and it then says that there's a Status 7 error.
After looking up Status 7 it says that it's usually a check that catches if you're not using the same model number that the ROM is for, but I clearly am as it's for the p5210 and I have the p5210. What am I doing wrong? Any help is much appreciated!
Q&A for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
bmx26 said:
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
Click to expand...
Click to collapse
Inside of drive, Try long pressing on it and clicking "download copy" it should download a copy to the downloads folder on your internal sdcard
using this rom cm12.1 for s3 sprint and its working great so far, only noticed two things........ camera not working and Battery but im going to see after a day or two if the battery last the same as the previous rom i was on cm12 (camera was working sort of with the camera zoom fx and viva video work around but i used high speed camera plus instead of camera zoom fx with viva video and it was good)............. so cant wait for a working camera or some kind of work around for this rom cm12.1 s3 sprint.......
Silly mod question.
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
brad2512 said:
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
Click to expand...
Click to collapse
The google drive link has the file
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Brisky86 said:
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Click to expand...
Click to collapse
it might. I was reading about some commits on github that broke cameras across the board, stock or from the play store. I tear laptops apart regularly enough to remember how, it's the process itself that sucks
After messaging mastamoon, "I imagine all the stuff that's being worked on is basically in d2-common, msm8960-common and d2kernel which d2spr shares with d2vzw. I would just make sure whoever is building for d2spr is pulling in all the necessary hacks needed at the moment. Honestly I'm not sure what isn't committed at this point, but check out commits by Dave Daynard (nardholio) & Dan Pasanen (invisiblek) and make sure you're using that stuff."
The kernel (within this ROM) he's speaking of might help with the issues revolving around the camera.
Camera Works
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Good to know thank hou
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
ChangeOfJinzo said:
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
Click to expand...
Click to collapse
Make sure you have the latest cwm recovery and you should be fine. I'd recommend flashify, I liked it better and seemed to function better then twrp manager. Also once you install twrp there's a method to update the recovery without a computer or making a recovery updater zip, which can also flash custom kernels. Though I recommend sticking with the stock kernel untill cm12.1 becomes more stable
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can anyone else confirm? I've yet to get this build in particular to boot...
iBlowpot said:
Can anyone else confirm? I've yet to get this build in particular to boot...
Click to expand...
Click to collapse
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
ChangeOfJinzo said:
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
Click to expand...
Click to collapse
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
iBlowpot said:
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
Click to expand...
Click to collapse
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Lrs121 said:
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Click to expand...
Click to collapse
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
iBlowpot said:
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
Click to expand...
Click to collapse
Probably a bad upload. I recommend using the new build.
FatalIll said:
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
Click to expand...
Click to collapse
also what bootloader and firmware version
Lrs121 said:
also what bootloader and firmware version
Click to expand...
Click to collapse
Hell, just give us your phone
Also, Lrs121... You had mentioned that you may try and cherry pick updates from other builds where the camera is working. I don't know much about cm source or building but have you considered using something like 'kaleidoscope git diff' to compare builds and see maybe where the camera fix is hiding?
Edit: not necessarily kaleidoscope, but git diff in general.