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...
Related
Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive:
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
Q&A for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]
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 [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]. 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!
Hi guys I did try it on my p601 and its ecelent
thought its easy just exported my modem on old p601 and tried to import it but I didnt make the trick
some other developer did mods for p601 then p600 maybe they can give a hint what else need to be done on a p601
ACTUALLY I use xkat 2.0 that developer did first an p601 and downgraded then a p600 version
would have no issue to use my device as p600 but get only internet by 3g
To get 3g to work requires a new device tree you can't just import your modem there will be a lot of files that need to call specific hard ware files, etc to get the 3g to work. I wish it was as simple as that
Sent from my SM-N9005 using Tapatalk
Does this Rom Have any Spen Support? Can anyone confirm?
cm12 how do i remove the mouse cursor?
As the question really. I am an artist and need to remove the onscreen mouse cursor when spen is used. I don't use an external mouse so dont mind losing it entirely.
Any ideas how?
Many thanks
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
WILDrBEAST said:
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
Click to expand...
Click to collapse
I don't have the camera issue,i dirty flashed like you are intending to.
Dirty flashing will fix the camera issue as in dirty flashing guy rom over raymanfx build or the nexus experience ... Some reason from source code the camera is not working. I want to build regular cm to check what portion I am missing (if any) of correct sources. I know what the error is from the logs however I fix one part and another crops up so I think there is something missing
Sent from my SM-N9005 using Tapatalk
Thanks!
I also think that this rom ir best of best.
Can anyone confirm pressure sensitivity is working? I cant find an answer, I read that spen is only a pointer so that does not work for drawing apps that use pressure?
My P600 came FedEx today and I'm ready to root and flash.
Should I update the device from P600UEUCNI1 to P600UEUCNK2 to get the latest KK recovery before I start? (if the 2 newer updates even makes changes to recovery).
I am getting the update prompt though it doesn't say which build.
The recovery shouldn't matter it will get flashed over with a twrp build anyway...
I am not up to date on the root ability of the newest bootloader as my device was rooted when I got it stock and I don't recall updating bootloader at any stage
Sent from my SM-N9005 using Tapatalk
problem when flashing
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
patrykket said:
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
Click to expand...
Click to collapse
Sounds to me that you are having problem with twrp recovery I had this when flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
joshndroid said:
Sounds to me that you are having problem with twrp recovery I had this whdden flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
Click to expand...
Click to collapse
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
Click to expand...
Click to collapse
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
joshndroid said:
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
Click to expand...
Click to collapse
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
patrykket said:
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
Click to expand...
Click to collapse
Please re-read my previous post.
I did not say manually flash rom, i was talking about the RECOVERY which is the TWRP recovery by using ODIN.
Please have a good read through guides, if the ones i linked don't help you try googling, there are plenty others. There are videos on youtube showing how to flash files/recovery using odin.
Please read as much as you can before starting, because when it goes bad no one is going to be able to fix it for you. As much as it is at your own risk i wouldn't like to see someone's hard earned money turn into a paperweight.
Tell me please, working s-pen?
The GPS is not working for me on this rom, heres what I did...
Step 1:
I flashed TWRP 2.6.3.3 with Odin 3.10,
Made a backup with TWRP,
Cleared Cache,
Cleared Dalvik,
Cleared Data,
Flashed cm-12-20141205,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Step 2:
Flashed cm-12-20141218,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Made a backup with TWRP,
Step 3:
Flashed cm-12-20150104 v4.2,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test does not work, neither does Navigation
Also tried "Step 3" with cm-12-20150103 v4.0 AND cm-12-20141231 v3.8 with the same result.
THIS ROM ROCKS! VERY SMOOTH AND FAST!!
Could this be a simple fix? did I take any incorrect steps?
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.
Please Delete the WiFi issue is no more this post did not solve the issue changing to a new rom did but caused other errors
reflash bluspark kernel.
you might have flashed magisk over bluspark which is the wrong order. always flash kernel last.
MarcTremonti said:
reflash bluspark kernel.
you might have flashed magisk over bluspark which is the wrong order. always flash kernel last.
Click to expand...
Click to collapse
Which would be completely pointless as you would lose everything magisk did. Magisk should be the last thing flashed
zelendel said:
Which would be completely pointless as you would lose everything magisk did. Magisk should be the last thing flashed
Click to expand...
Click to collapse
Sorry but thats wrong.
Something to read for you:
https://forum.xda-developers.com/showpost.php?p=72996757&postcount=5886
https://forum.xda-developers.com/showpost.php?p=72984150&postcount=5880
Last link is a post from the dev of bluspark kernel btw.
I'm still unable to mount storage via TWRP, if anyone can help and maybe needs more information to do so, just tell me what you need, this is a huge problem for me, I don't know what to do?
Re-flash TWRP?
Not being able to do anything with my recovery really makes me scared to do anything with my phone, when try new apps.
I appreciate anything anyone can do to help me, even just reading this post and giving it a shot is great, any replies would be awesome, this issue occured directly after I flashed RR ROM
MarcTremonti said:
Sorry but thats wrong.
Something to read for you:
https://forum.xda-developers.com/showpost.php?p=72996757&postcount=5886
https://forum.xda-developers.com/showpost.php?p=72984150&postcount=5880
Last link is a post from the dev of bluspark kernel btw.
Click to expand...
Click to collapse
And he is wrong. Check the majisk thread. Or even just thing about it for a second. If majisk makes changes to the kernel and then you flash a new one, what happens?
Never take anyone's word without doing your own research. Look into it and you will see.
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
lebeatnik said:
I'm still unable to mount storage via TWRP, if anyone can help and maybe needs more information to do so, just tell me what you need, this is a huge problem for me, I don't know what to do?
Re-flash TWRP?
Not being able to do anything with my recovery really makes me scared to do anything with my phone, when try new apps.
I appreciate anything anyone can do to help me, even just reading this post and giving it a shot is great, any replies would be awesome, this issue occured directly after I flashed RR ROM
Click to expand...
Click to collapse
By any chance is your system encrypted? I know recovery had an issue with encrypted devices for a while. Can't be sure as I never run encrypted and it's the first thing I remove when getting a new divice.
zelendel said:
And he is wrong. Check the majisk thread. Or even just thing about it for a second. If majisk makes changes to the kernel and then you flash a new one, what happens?
Click to expand...
Click to collapse
Well what happens is that magisk is working fine and new kernel also.
If flashed the other way around like you suggest i end up with broken wifi, and not only me (check bluspark thread).
So flashing like eng.stk advises, magisk first, then bluspark everything is running fine, so...
MarcTremonti said:
Well what happens is that magisk is working fine and new kernel also.
If flashed the other way around like you suggest i end up with broken wifi, and not only me (check bluspark thread).
So flashing like eng.stk advises, magisk first, then bluspark everything is running fine, so...
Click to expand...
Click to collapse
The I will tell you that something is wrong. As I never and I mean never have that issue but then again I don't use that kernel. But have not had the issue with the kernels I have used.