Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, catches fire, you get fired because the alarm failed, and global thermonuclear war
Kali Nethunter ported to the Samsung Galaxy S3​REQUIREMENTS:
A Samsung Galaxy S3 USA CURRENTLY RUNNING CM11 failure to have this will result in a brick and possibly even a HARD BRICK
A functioning brain
A working recovery
Basic instruction following skills
STEPS:
Download the two zips and copy them to your phone
Link for file 1: https://drive.google.com/open?id=0B5BIHhwzM7wWdDhnbW9xR0E3d2M
Line for file 2: https://drive.google.com/file/d/0B5BIHhwzM7wWSDA5MmZmMjN1TFE/view?usp=sharing
Reboot into recovery
Flash the zips in either order.
???
Profit.
Use make kali_defconfig to make the Kali Kernel correctly if compiling
Please post flash time and results below, this should work on ALL d2 devices under the d2lte label CM uses.
XDA:DevDB Information
Kali Nethunter for d2lte , ROM for the Sprint Samsung Galaxy S III
Contributors
dank101
Source Code: https://bitbucket.org/dank101/android_kernel_samsung_d2_kali
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: CM11
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 0.1
Beta Release Date: 2015-06-09
Created 2015-06-10
Last Updated 2015-07-08
WooHoo!
hotwired34 said:
WooHoo!
Click to expand...
Click to collapse
FYI: I just updated the kernel zip to fix approximately everything.
I am trying to make a port for cm12.1 d2att could you upload the device scripts.
aron2hip said:
I am trying to make a port for cm12.1 d2att could you upload the device scripts.
Click to expand...
Click to collapse
Uhhh....
Not that easy...
Also ask on the d2att thread.
dank101 said:
Uhhh....
Not that easy...
Also ask on the d2att thread.
Click to expand...
Click to collapse
I have the kernel source in the devices directory, I'm just too lazy to edit the androidmenu bash script for the device. Unless there are further modifications necessary.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
aron2hip said:
I have the kernel source in the devices directory, I'm just too lazy to edit the androidmenu bash script for the device. Unless there are further modifications necessary.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
There are indeed future mods needed.
The first two Google Drive links are dead.
Here is a mirror for the files. I don't know how long they will last so urge OP for new mirror.
http://www.filedropper.com/kalilinuxnethunter121d2ltekitkat
946mb
http://www.filedropper.com/kalinhkernel
12.5mb
Knuxyl said:
The first two Google Drive links are dead.
Here is a mirror for the files. I don't know how long they will last so urge OP for new mirror.
http://www.filedropper.com/kalilinuxnethunter121d2ltekitkat
946mb
http://www.filedropper.com/kalinhkernel
12.5mb
Click to expand...
Click to collapse
You really should have PMed me about this FIRST.
I didn't know they died.
When will file links be available for download again cause? I was only ever able to download the kali kernel!
Flashed cm11 plus all zips , rom boots fine. Except for the part where the screen doesn't display anything (stays blank and off), however I can swipe to unlock and get the vibration as well as turn the volume up and down and get the sound that is associated. Any ideas I've done it twice with full wipes of everything I could wipe asside from the sd card
balves08 said:
Flashed cm11 plus all zips , rom boots fine. Except for the part where the screen doesn't display anything (stays blank and off), however I can swipe to unlock and get the vibration as well as turn the volume up and down and get the sound that is associated. Any ideas I've done it twice with full wipes of everything I could wipe asside from the sd card
Click to expand...
Click to collapse
You're doing it wrong.
You don't wipe anything.
dank101 said:
You're doing it wrong.
You don't wipe anything.
Click to expand...
Click to collapse
Im not wiping between installing cm11 and the two zips, that's stupidity. I was doing a full wipe before reflashing cm11 and the 2 zips again. Just no display
balves08 said:
Im not wiping between installing cm11 and the two zips, that's stupidity. I was doing a full wipe before reflashing cm11 and the 2 zips again. Just no display
Click to expand...
Click to collapse
I don't understand how that could be happening....
It's working on my S3 fine. And the nethunter zips are just a kernel and a zip that runs a bunch of scripts and extracts a CHROOT.
dank101 said:
I don't understand how that could be happening....
It's working on my S3 fine. And the nethunter zips are just a kernel and a zip that runs a bunch of scripts and extracts a CHROOT.
Click to expand...
Click to collapse
Do you think that it would have anything to do with what version of cm11 that is being used, I r what baseband? (I'm noob ish when it comes to that) cuz cm11 works fine then I flash everything and it shows the Droid logo or w/e and then goes blank with the soft keys illuminating, as well as responding to touch (side note I had forgotten to authenticate the adb connection prior so I could easily reboot to recovery and was able to bring up and select ok to allow it w/o the screen being visible, so it must be something driver related to the display)
balves08 said:
Do you think that it would have anything to do with what version of cm11 that is being used, I r what baseband? (I'm noob ish when it comes to that) cuz cm11 works fine then I flash everything and it shows the Droid logo or w/e and then goes blank with the soft keys illuminating, as well as responding to touch (side note I had forgotten to authenticate the adb connection prior so I could easily reboot to recovery and was able to bring up and select ok to allow it w/o the screen being visible, so it must be something driver related to the display)
Click to expand...
Click to collapse
Try flashing CM11 without flashing nethunter, if the display is working, then I dunno what to say.
dank101 said:
Try flashing CM11 without flashing nethunter, if the display is working, then I dunno what to say.
Click to expand...
Click to collapse
Done that 3 times cm11 works fine, display goes to **** after flashing nethunter. What version of cm11 are you using by the way
Clean flash over 04/26 nightly took about 20 mins. No issues so far I got some more playing around to do before a final verdict. Thanks I'll have some fun with this.
balves08 said:
Done that 3 times cm11 works fine, display goes to **** after flashing nethunter. What version of cm11 are you using by the way
Click to expand...
Click to collapse
Personally I used the d2lte latest nightly.
What good is this to the S3? I wasn't aware that this phone can go into monitor mode at all.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
REQUIREMENTS
Click to expand...
Click to collapse
- TF300T (it can be installed on TF300TG but no 3G support!)
- Unlocked bootloader
- Your bootloader must be at least on Jelly Bean version (10.4 and above). - We recommend that you run the 4.2 Bootloader.
DOWNLOADS
Click to expand...
Click to collapse
Google Apps:
http://goo.im/gapps
Nightlies:
http://get.cm/?device=tf300t
HOW TO INSTALL
Click to expand...
Click to collapse
First installation :
1) Unlock your device, and install TWRP recovery (look in the development forum for the thread)
2) Push the update zip to your internal memory
3) Reboot in recovery (Shutdown tablet, press Vol Down + Power, then press Vol Up when prompted)
4) Make a backup
5) Navigate to "Install zip from sdcard", "Choose zip from sdcard", and choose the update zip you previously pushed to your tablet
5a) If you want Play Store, flash gapps now too (link above)
6) Go back and Wipe data/cache
7) Reboot
Updating from previous build:
1) Push update zip to /sdcard/
2) Reboot in recovery
3) Flash as above
4) Reboot
If any issue after updating, wipe data.
CHANGELOG
Click to expand...
Click to collapse
http://changelog.bbqdroid.org/#tf300t/cm10.1/next
SOURCES
Click to expand...
Click to collapse
http://github.com/cyanogenmod
http://github.com/cyanogenmod/android_kernel_asus_tf300t
http://github.com/cyanogenmod/android_device_asus_tf300t
DEVELOPERS
Click to expand...
Click to collapse
xplodwild, bumble-bee (for tf201 device tree from which this tree is inspired), chrmhoffmann, loganmc10, dasunsrule32 for some help, cyanogenmod
SUPPORT US
Click to expand...
Click to collapse
You can either help us by giving FULL bug reports WITH LOGS, WITH REPRO CASE, ETC, or by submitting patches.
If you're not a developer, but still want to support you can hit the "Donate to me" button up ahead. Chrmhoffmann, please remind me to give you some of it - Remember this is something we're doing in our free time, so a small gift is always appreciated and motivates us to keep on updating the port Thanks to all donators!
Woot thanks man, appeciate it!
Tears of Joy
Well almost anyways.
Anyone else getting FC every time the AOSP keyboard try's to popup ?
EDIT: reflashed without gapps and it's fine, but as soon as I flash gapps the FC come back on popup keyboard. Otherwise rom seems fast, everything else seems ok at first glance but I flashed back to a backup cause the ROM in unusable without the keyboard.
So we don't have to be on the 4.2 bootloader for this to work? 4.1 bootloader will be fine?
zaki0saad said:
So we don't have to be on the 4.2 bootloader for this to work? 4.1 bootloader will be fine?
Click to expand...
Click to collapse
The 4.2 Bootloader is preferred, but I have only tested it on the 4.2 bootloadee (my own build). Off course you can try if you are still on the 4.1 bootloader. If the ROM does not boot, then you will know
Sent from my Nexus 10 using Tapatalk 4
zurny said:
Anyone else getting FC every time the AOSP keyboard try's to popup ?
EDIT: reflashed without gapps and it's fine, but as soon as I flash gapps the FC come back on popup keyboard. Otherwise rom seems fast, everything else seems ok at first glance but I flashed back to a backup cause the ROM in unusable without the keyboard.
Click to expand...
Click to collapse
Did you build yourself? Because there is no nightly build yet to download.
If you downloaded the latest nightly from get.cm, and flashed the 4.3 gapps then it would be a bit logical that you get a fc because you flashed 4.3 gapps on a 4.2.2 build.
Sent from my Nexus 10 using Tapatalk 4
Great! Waiting patiently for the official thing
joelalmeidaptg said:
Great! Waiting patiently for the official thing
Click to expand...
Click to collapse
Yeah, that same feeling when he made a post for CM10.1 and wait for a while to get it haha.
scanno said:
Did you build yourself? Because there is no nightly build yet to download.
If you downloaded the latest nightly from get.cm, and flashed the 4.3 gapps then it would be a bit logical that you get a fc because you flashed 4.3 gapps on a 4.2.2 build.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Wow I feel an idiot, looks like I flashed 10.1, I looked at the release date but didn't check the filename, carry on, nothing to see here
glad for your repaired tf300
After I saw that you recommended CWM for this ROM, I downloaded and flashed it. It ****ed up my device, only allowing me into CWM, not even fastboot. That gives me ADB, but CWM wont mount anything, so I cant flash anything...PLEASE HELP ME!!!
I believe you need TWRP 2.5 instead
kriscodian said:
After I saw that you recommended CWM for this ROM, I downloaded and flashed it. It ****ed up my device, only allowing me into CWM, not even fastboot. That gives me ADB, but CWM wont mount anything, so I cant flash anything...PLEASE HELP ME!!!
Click to expand...
Click to collapse
The new bootloader requires TWRP 2.5 instead - I am a firm believer in CM recovery for all my recovery needs except this. Please correct me if I am wrong, but currently as far as I know, TWRP 2.5 is the only recovery that works with the new Android 4.2+ bootloader. Check the basic threads for the background.
kjwaugh said:
The new bootloader requires TWRP 2.5 instead - I am a firm believer in CM recovery for all my recovery needs except this. Please correct me if I am wrong, but currently as far as I know, TWRP 2.5 is the only recovery that works with the new Android 4.2+ bootloader. Check the basic threads for the background.
Click to expand...
Click to collapse
I was on TWRP 2.5.0.0, but in the instructions in this ROM it said CWM. Now I can't flash Recoverys or anything...
What can I do to fix it?
Try the CWM Recovery thread
kriscodian said:
I was on TWRP 2.5.0.0, but in the instructions in this ROM it said CWM. Now I can't flash Recoverys or anything...
What can I do to fix it?
Click to expand...
Click to collapse
You were already there - try the link below:
http://forum.xda-developers.com/showthread.php?t=1668173&page=46
It covers the basics and shows the "new" fastboot mode aswell as the current state of this "new" bootloader requiring TWRP 2.5
Can I update from 10.1? In my galaxy s the partition layout for 10.2 is different from the 10.1 cm so it required a full wipe.
Thanks
Sent from my TF300T using Tapatalk 2
kjwaugh said:
You were already there - try the link below:
http://forum.xda-developers.com/showthread.php?t=1668173&page=46
It covers the basics and shows the "new" fastboot mode aswell as the current state of this "new" bootloader requiring TWRP 2.5
Click to expand...
Click to collapse
But neither of the methods work as I am not allowed into Those choices... It goes straight into CWM, no fastboot
kriscodian said:
But neither of the methods work as I am not allowed into Those choices... It goes straight into CWM, no fastboot
Click to expand...
Click to collapse
Make sure you have adb drivers installed when you are in CWM (check in device manager on pc) and then try typing adb reboot bootloader in adb.
Already tried...
Start at the beginning then
kriscodian said:
Already tried...
Click to expand...
Click to collapse
Install Asus stock rom, then install recovery, root it, factory reset and then continue with usual rom-flashing instructions.
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
EDIT: Typo corrected in OP.
dansou901 said:
Kindle Fire HD 7? In Oneplus One section?
Click to expand...
Click to collapse
sorry typo error. Recovery is for oneplus
@acer73 any chance at compiling the touch version?
dmo580 said:
@acer73 any chance at compiling the touch version?
Click to expand...
Click to collapse
This is last ver with swipe (touch)
acer73 said:
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
Click to expand...
Click to collapse
grazie mille
ha qualche bug ?
Don't quote OP and please use English.
good news!thanks!
Dualboot
Hi everyone
I have a Xiaomi M2s right now and the thing i like the most about the device is that it has 2 system partitions and that I can install MIUI on my first partition and CM11 on my second partition. This is ideal if you want to test a ROM but keep one stable system.
Is there any chance that there will be a way to re-partition the one plus to have this? Also CMW would need to have true dual boot right or is this a stock feature?
I don't know if partitioning is common on other devices?
The backups created appear to not have the correct dates for filenames. They start with 1970...
Is this a offical build? Will it be listened on clockworkmod.com anytime soon?
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
fiz:ik said:
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
Click to expand...
Click to collapse
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Had the problem with Mahdi rom and Philz or cwm ... Hope they will fix this soon !
I found this .. Not really perfect :/ http://forum.xda-developers.com/showpost.php?p=54112729&postcount=24
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm on stock CM11S
I'm try to build a lot of rom but all of these bootloop or take a lot of time to start, or data partition unmount itself after a reboot.
No issue using PA version 20140708
So I think there is some issue in the last sources,otherwise if it was a problem of recovery also paranoid should have bootloop.
Now I'm trying to build PA with last sources
what about an update?touch edition?
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
Would be great, I hate TWRP and Philz, too. CWM is sufficient, but this project here looks abandoned
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
wacky.ddw said:
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
Click to expand...
Click to collapse
no problems in all my phones with touch
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Recovery Package [Goo]
http://goo.im/devs/playground/trltesku/
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4/unified-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltetmo
[Recovery]Philz Touch Recovery - Ported to North America
The initial version uses a kernel for the N910W8 and SELinux policy settings from the N910T. If that combination works for me, I can almost guarantee it will work on either of those devices because those values would not match up.
re: Philz Custom Recovery
twistedumbrella said:
Original Thread by Philz3759: http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo
http://goo.im/devs/playground/trltetmo/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel and some other minor tweak that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Click to expand...
Click to collapse
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Misterjunky said:
Thanks for sharing Philz Touch Recovery for our N910T, it's always good to
have a backup custom recovery just in case twrp ever stops working properly.
Click to expand...
Click to collapse
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Kernel control apps
twistedumbrella said:
Yeah, I used to just make my own but it's far easier to outsource the core and then replace it with the kernel I'm already working on.
Click to expand...
Click to collapse
Just out of curiosity, in your opinion what is the best app at the play store which
is fully compatible and easy to use with your StarKissed kernels that even noobs
can use without fear of messing anything up when changing the kernel settings?
Thanks!
Thanks.....will wait for corrected upload
louforgiveno said:
Thanks.....will wait for corrected upload
Click to expand...
Click to collapse
It should be uploaded in the next minute or two to Mega and shortly after for Goo
These links not working?
Hanoverfiste said:
These links not working?
Click to expand...
Click to collapse
They should be. I just tried them and they did
twistedumbrella said:
They should be. I just tried them and they did
Click to expand...
Click to collapse
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Hanoverfiste said:
I read back and saw where Tapatalk won't work properly, so I tried through Chrome and that's not working either.
Click to expand...
Click to collapse
Mega was the issue on the device, so there is a Goo mirror below it. That should be working.
Or it would have been if I remembered I changed folders on Goo. Now it does.
twistedumbrella said:
Original Thread by Philz3759:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltexx-philz-touch-t2927930
Download from Mega:
https://mega.co.nz/#F!l1RBBbDI!KHcF184rkhshJhdF_tO7gw
Download from Goo:
http://goo.im/devs/playground/trltesku/recovery
This is the CWM-based Philz Touch Recovery with a shiny new kernel, SELinux tweaks, and some other modifications that enable it to run on the N910T and N910W8 out of the box.
May also run on the Sprint and AT&T variants, but make sure to have a copy of a working recovery handy in case you need to restore.
Kernel: http://forum.xda-developers.com/note-4-tmobile/orig-development/kernel-dealers-choice-t2915824
Device: https://github.com/StarKissed/android_device_samsung_trltephil
Click to expand...
Click to collapse
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
sunnyo_ola said:
Guys, I don`t know if I am doing something wrong.
I have been using Twrp 2.8.1.1, I used it to flash CWM.
I tried to back up using CWM but says error while making a backup image of /data!
please press any key to continue.
I need help please!
Click to expand...
Click to collapse
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
twistedumbrella said:
The partition scheme may be off. I assumed there were identical from Europe to NA but I'll verify that tonight
Click to expand...
Click to collapse
Thank you, I am using US T-Mobile note 4!
Yeah... The partition scheme is off. I'm on T-Mobile and it won't work. Thanks for your efforts and I can't wait to try again.
[Recovery]Philz Touch Recovery[North American Variants]
Edit: nevermind. The issue is obviously deeper than the fstab or SELinux
Thanks for your hard work. I'm happy to test if you need anything.
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
twistedumbrella said:
After a lot of building, rebuilding, reconfiguring, etc some new builds are finally up.
The current version only supports identifying itself as a T-Mobile device until fully tested.
Rather than modifying the existing European version for the US, this now fully source-built.
Click to expand...
Click to collapse
Thank you I am going to try it right now,
I will you a feedback.
thank you again for the great work always!
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.
Introduction
This is a flashable zip of the latest Stock ROM for the Nextbit Robin. The boot.img is modified with removed DM-Verity and forceencryption.
It contains no recovery.img so you can continue using TWRP.
Installation
Clean flash:
- Download latest build
- Boot TWRP
- Wipe system, data, cache, and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Dirty flash:
- Download latest build
- Boot TWRP
- Wipe cache and dalvik cache
- Flash ROM zip
- Flash other zips (such as root and kernels)
- Reboot
Download
ROM: https://www.androidfilehost.com/?fid=673368273298967045
XDA:DevDB Information
Nextbit Robin - ether - Flashable Stock ROM, ROM for the Nextbit Robin
Contributors
crian
Source Code: https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
ROM OS Version: 7.x Nougat
Based On: Stock
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-25
Awesome thanks!
I've tried to use Substratum with this ROM but it won't work. Anyone successful?
jir591 said:
I've tried to use Substratum with this ROM but it won't work. Anyone successful?
Click to expand...
Click to collapse
It's stock and not compatible with oms.
A Mega mirror if possible? Thanks. AFH is taking too long.
I've uploaded it to MEGA
Let me know if you want me to delete the link
Hi is this stock the same and included also the 100 go memory cloud ?
Mchasard said:
Hi is this stock the same and included also the 100 go memory cloud ?
Click to expand...
Click to collapse
Yes
Sent from my Robin using Tapatalk
kwattro76 said:
Yes
Click to expand...
Click to collapse
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...
Mchasard said:
Thanks for your answer otherwise the size of this ROM is big 1.2go oops...
Click to expand...
Click to collapse
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Sent from my Robin using Tapatalk
kwattro76 said:
That's about right. If you take a vanilla nougat rom and and then add the largest gapp package you there you have it.
Click to expand...
Click to collapse
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?
Mchasard said:
OK it's due to the largest gapps ... Generally I'm using pico not the largest... Thanks
Is there a way to root to delete some system apps?
Click to expand...
Click to collapse
Just flash your favorite su app and delete some system apps.
This is just a flashable zip of the stock rom. So there are the same gapps as the factory image got.
Anyone try that unofficial xposed on this rom?
Sent from my Robin using Tapatalk
Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?
bilged said:
Thanks this is great. All the custom roms have too many stability bugs to be reliable enough for a daily phone. As this is stock with no recovery though, could I relock the bootloader while keeping twrp and root - therefore getting rid of the warning message on boot? Would this cause problems?
Click to expand...
Click to collapse
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.
/root said:
Omni and LOS works fine for me. Seems pretty table overall to me for daily use.
Anyway to answer your question, locking the bootloader will require you to flash the stock recovery which means you will lose TWRP as TWRP is the custom recovery that replaces the stock recovery.
When you root the device you are modifying the boot.img and system partitions so it won't be advisable to lock the device and try to keep root as it might not function properly and worse could brick your device. Because if anything goes wrong and your bootloader is locked there is no way to fix that issue, the point of keeping a custom recovery is so that you can fix any problem that could arise because of the modified system files.
Click to expand...
Click to collapse
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.
bilged said:
Ok got it. Thanks for the quick answer. As for the roms, I was using Omni but I was getting crashes when using GPS (Waze) and nfc never seemed to work reliably. I switched to LOS when Omni stopped updating but I've had similar issues with it as well. Stock works well but it would be nice to have up to date security patches.
Click to expand...
Click to collapse
I am currently using LOS but was on Omni most of the time as Omni was really stable and updated that time. But Omni started eating a lot of battery and stopped providing updates, so I switched to LOS as soon as LOS 15 was released for Robin. GPS worked fine for me on Omni too, it sometimes had problem locking the location but navigation on Google Maps worked as it should. Waze I used a few times it didn't crash that time. But not a regular Waze user.
Did your clean flash the ROM?
Can't tell you about NFC as I sadly have no reason to use it.
By the way, how is your battery? Mine is degrading bad. My SOT has gone from 3-4hrs to 2-2.5hrs. over the 2+ years of owning this device. Not only that, below 30-40% it would shut down on running any heavy app like Camera or Maps or Music Streaming. Battery is degrading badly.