Vyper Kernel
Code:
[SIZE="4"]*** Disclamer***
* Your warranty is now void.*
* We are 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 us for messing up your device, we will laugh at you.[/SIZE]
Specs:
Linux: 3.10.61
Based on: J700TUVU3BQI5
Features:
Permissive
Samsung root restrictions removed
More to come...
Changelogs
Version 1 (10/27/17)
Initial Release
Set to permissive
Samsung root restriction removed
Instructions
Download the boot.img and encrpytion breaker and place it in the phone
Boot into recovery
Install > Install Image
Select the boot.img and then select the Boot button
Flash encryption breakerDownloads
Version 1
Code:
[url]https://drive.google.com/open?id=0B4jcHuuXWg4ANl9hcGpsWlRsaXc[/url]
Encryption Breaker
Code:
[url]https://drive.google.com/open?id=0B4jcHuuXWg4AQ3c1ZDRTUFBRaG8[/url]
Stay tuned for more. I am planning on a lot of good stuff
Source Code -
https://github.com/vekenti/Vyper_Kernel
Thanks to:
Ashyx for encryption breaker.
All my friends that kept on yelling at me to make this. You know who you are.
Awesome job bro! Now the roms can come :highfive:
Excellent work bro ??
Yay I knew u had it in you bro
Man you need to post more, we gotta get you elavated to senior member. Can't have noobs posting kernels now
Thank u. Thank u. Thank u. This is soo right on time.
Now the fun can begin!
Successful install in my j1 submerge.:cyclops:
fullofhell said:
Successful install in my j1 submerge.:cyclops:
Click to expand...
Click to collapse
and we have the kernel just missing ROM ?
carlosbalbuena_ said:
and we have the kernel just missing ROM ?
Click to expand...
Click to collapse
Ok have a couple done, but there not good enough..hang tight boys, theyre coming.
Still waiting on those tombstones fellah.
fullofhell said:
Ok have a couple done, but there not good enough..hang tight boys, theyre coming.
Click to expand...
Click to collapse
Metabolic12 said:
Still waiting on those tombstones fellah.
Click to expand...
Click to collapse
I forgot. Sorry.
Ok, so I kinda have a working beefed up stock rom with all the pizazz going with your kernel, I just added initd support and removed the rest of the encryption congrats man u are the kernel boss now. Testing it out to see if I finally fixes aod and edge..it's probably gonna make my phone melt.
My phone hangs on T-Mobile boot logo after flashing this in TWRP. :/
It takes a while man
fullofhell said:
It takes a while man
Click to expand...
Click to collapse
For just first boot? I gave up and flashed stock kernel after rebooting twice, should I go back? If that boot time is every boot Idk if that's worth
phoen1x74 said:
For just first boot? I gave up and flashed stock kernel after rebooting twice, should I go back? If that boot time is every boot Idk if that's worth
Click to expand...
Click to collapse
It's just the first boot. A kernel is what the hardware uses to communicate with the software so it does have to take a few minutes because it's writing all the information as like a intermediary
phoen1x74 said:
For just first boot? I gave up and flashed stock kernel after rebooting twice, should I go back? If that boot time is every boot Idk if that's worth
Click to expand...
Click to collapse
Only first boot. Try flashing again and then let it sit on logo for a while, it shouldnt take longer than 20 minutes or so for first boot. After that it takes about same amount of time to boot.
Did you flash supersu or Magisk after flashing the kernel?
phoen1x74 said:
For just first boot? I gave up and flashed stock kernel after rebooting twice, should I go back? If that boot time is every boot Idk if that's worth
Click to expand...
Click to collapse
Fyi I got magisk 14 and supersu systemless both installed and booted with this kernel. Not like together or anything weird..but I tried both
Thanks for releasing a permissive nougat kernel
I've never compiled a Sammy Kernel... for starters I've tweaked the SELinux Makefile.
Having issues.... can you release your source?.github?
Related
While it is uploading here is the info. We have been working on making a custom recovery. No luck. Close but not there yet. So I decided to make a pre-rooted firmware you can flash through Odin. Works perfectly. The firmware I used was for the UK version. Funny enough stock the kernel is unsecure. Anyways it is the whole firmware so it is about 1.1-1.2 gigs. Uploading to me Dev-host.
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.
*/
By using the rom you agree with the above terms!
Instructions:
Download firmware
Download Odin - Link here
Boot into download. (either hold power and volume down or do adb reboot download)
Click on PDA and then find prerooted.tar.md5
MAKE SURE RE-PARTITION IS NOT CHECKED!!! You will have an instant brick! You have been warned.
Click start and wait.
once done it will reboot into (stock) recovery and finish installing.
Once done and booted just open SuperSU and update the binary. Not by CWM but the other.
Done. Enjoy!
Rooted firmware (UK - SM-T210) - http://d-h.st/leL
SM-T210R - http://d-h.st/bCi
Link to download stock UK firmware to revert if need be.
here is the download
http://www.hotfile.com/dl/236716450/7b9164c/T210XXAMG2_T210OXXAMG1_BTU.zip.html
one more
Firmware
Sent from my SM-T210 using Tapatalk 4 Beta
Awesome! Thanks for your dedication and hard work.
Sent from my XT926 using Tapatalk 2
Thanks man. Was driving me nuts. Now recovery. Already got the kernel going.
Worked perfectly man....outstanding Now rooted!!!
Sent from my SM-T210 using xda app-developers app
do you have a md5 checkfile?
i want to check if the file is corrupted before i flash it
EDIT:
...okay sorry... it's late here... xD
there already is a md5 checknumber...
lorender_ruffy said:
do you have a md5 checkfile?
i want to check if the file is corrupted before i flash it
Click to expand...
Click to collapse
The md5 is on the download page (and odin will check it too).
Sent from my SM-T210 using xda app-developers app
what version of odin is every one using for the tab 3
Hey!!!! Congrats man....
Just two questions
1. That 'instant brick' you talk about... You mean a HARD unrepairable brick x.x? (Want to be aware of everything that can go wrong haha)
2. This will obviously erase all my data right?
Sent from my SM-T210 using xda premium
mirrin said:
what version of odin is every one using for the tab 3
Click to expand...
Click to collapse
The 3.07 version from the link in the first post works fine for me.
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
FiliBrushedRed said:
Hey!!!! Congrats man....
Just two questions
1. That 'instant brick' you talk about... You mean a HARD unrepairable brick x.x? (Want to be aware of everything that can go wrong haha)
2. This will obviously erase all my data right?
Sent from my SM-T210 using xda premium
Click to expand...
Click to collapse
Not sure about the first question, but you should not lose your data. This flash does not erase or overwrite the data folder (at least I didn't lose mine).
If repartition is checked it will hard brick the device. Any Samsung device actually. This is an Odin issue and has nothing to do with the firmware. Just double check repartition is not checked and you have nothing to worry about.
Just warning people who haven't used Odin before and thought that was how to wipe like recovery. It is not! This deleted recovery, download mode and even the boot partition. Lights go out and never return.
Jamison904 said:
If repartition is checked it will hard brick the device. Any Samsung device actually. This is an Odin issue and has nothing to do with the firmware. Just double check repartition is not checked and you have nothing to worry about.
Just warning people who haven't used Odin before and thought that was how to wipe like recovery. It is not! This deleted recovery, download mode and even the boot partition. Lights go out and never return.
Click to expand...
Click to collapse
yeah i knew that much odin is serious business very easy to brick if you do it wrong. one of many reasons i have been hoping to get a easy root and unlock up for the na firmware this solution is putting the uk firmware on the na device same hardware just a few bits flipped in the na version i keep trying to keep my self convinced to wait for safer methods and roms to get released but i miss root so much...
Well besides that and making sure you have enought battery life this is very safe. I flashed like 20 other failed attempts of custom recovery and this like 2-3 times getting it 100% correct.
Sent from my SM-T210 using Tapatalk 4 Beta
This is only root right no recovery
menu151 said:
This is only root right no recovery
Click to expand...
Click to collapse
Yep full UK ROM pre rooted since apparently the r in sm-t210r stands for restricted.
can i do this on SM-T210? (Hong Kong/ Taiwan version)
I've done ist successfully on a SM-T210 sold in Germany...
Only thing i noticed is a slight problem with GPS.
It takes long to find sats and even after a minute or so only 3
sats were found. With the "stock" Rom around 10 sats were found
in less than a minute...
Other than that it works fine ! Congrats !
Cant wait to see custom roms coming...
Regards
Joachim
Thanks man. Already have the first release ready. Just working on a functional recovery.
Pre-Rooted ROMDeoxexed: V3
Non-deodexed: V2
Code:
Disclaimer
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead pets, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, We will
* laugh at you. Loud and hard.
*/
Information:
Standard version~
Pre-rooted
Deodexed
Zipaligned
Default Linux policy to permisive
Busybox installed
Alternate version~
Pre-Rooted
Debloated
Install instructions
1. Download to Device
2. Install
3. wipe dalvik and Cache
4. wipe data (if needed)
[NOT NEEDED IF YOUR ALREADY ON 167]
5. for Locked bootloader users, i recomend flashing this rom THEN Flashing a .167 FTF excluding System.sin
5. FOR UNLOCKED BOOTLOADERSFlash Advanced Stock kernel V7 from doomlord for
Download
deoxex Version
https://docs.google.com/file/d/0B7kXPU2Y8c5xcWNUbHJrcnoxdGs/edit?usp=docslist_api
non-deodex Version
https://mega.co.nz/#F!NNZGHYRI!2SFBnPq5RAW2C-4aez6wNQ
(install V1 then V2)
If root Fails Flash this
http://download.chainfire.eu/supersu
Bugs
BUG FREE \m/
(atleast from my testing)
Can I install on uk firmware?
My bootloader is locked, how to delete System.sin installation?
Works best with cwm or TWRP?
Thank you for your work!
caslubas said:
Can I install on uk firmware?
My bootloader is locked, how to delete System.sin installation?
Works best with cwm or TWRP?
Thank you for your work!
Click to expand...
Click to collapse
-In flashtool->Flasmode->Exclude = Check SYSTEM
-In my case... I preferd CWM...
I am uploading a flashable zip of an alternate version
It is just a Debloated and Pre-Rooted rom
It fully works from my testing
I kinda hate how xda-premium doesnt alow attatching to already posted posts
Is it a complete rom?Or a flashable zip which only includes deodexed app,priv-app and framework files?
Failed to download from google drive. It hanging for long time.
Quisland said:
Is it a complete rom?Or a flashable zip which only includes deodexed app,priv-app and framework files?
Click to expand...
Click to collapse
Its full zip
kumbangdesa said:
Failed to download from google drive. It hanging for long time.
Click to expand...
Click to collapse
Ill try mirroring
Unless someone else can help
I created using PRF creator but I couldn't mount the system partition RW. Did anyone can confirm that,
Sent from my D6503 using Tapatalk
kamalmawa said:
I created using PRF creator but I couldn't mount the system partition RW. Did anyone can confirm that,
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes some other users had the issue too
You have to copy some files before hand and you also have to edit the updater script
I feel like a damn idiot!!!!
Working on update now
I think ive figured out the FC, there is a "setenforce 0" command at the end of init_qcom_post_boot.sh in /etc
Change it to 1 or remove it, it fixes some FCs
Ill fix when i have free time
Its 5:42AM and i have to go college soon
Envious_Data said:
I feel like a damn idiot!!!!
Working on update now
I think ive figured out the FC, there is a "setenforce 0" command at the end of init_qcom_post_boot.sh in /etc
Change it to 1 or remove it, it fixes some FCs
Ill fix when i have free time
Its 5:42AM and i have to go college soon
Click to expand...
Click to collapse
Good man enjoy college buddy!
Can I confirm you are able to mount system?
Sent from my D6503 using XDA Free mobile app
Is 5th step required when conning from rooted stock (UK H3G fw .314).
As currently I am unable to boot(stuck on the Sony sign when I power up the device) after I flashed v1 (wiped cache and dalvik after install) and then flashed V2 without rebooting beforehand.
I have the 03 variant with unlocked bootloader. Flashed using CWM 6.0.5.0
DaGhostman said:
Is 5th step required when conning from rooted stock (UK H3G fw .314).
As currently I am unable to boot(stuck on the Sony sign when I power up the device) after I flashed v1 (wiped cache and dalvik after install) and then flashed V2 without rebooting beforehand.
I have the 03 variant with unlocked bootloader. Flashed using CWM 6.0.5.0
Click to expand...
Click to collapse
FOR UNLOCKED BOOTLOADERS Flash Advanced Stock kernel V7 from doomlord.
RIght from the OP.
Thank you for your contribution
Is step 5 also needed if you are already on .167?
CorzCorry said:
Thank you for your contribution
Is step 5 also needed if you are already on .167?
Click to expand...
Click to collapse
Already on 167 Nope
mik101 said:
FOR UNLOCKED BOOTLOADERS Flash Advanced Stock kernel V7 from doomlord.
RIght from the OP.
Click to expand...
Click to collapse
The part with '#partially mandatory' confused me a bit, I thought that it is optional but advisable.
DaGhostman said:
The part with '#partially mandatory' confused me a bit, I thought that it is optional but advisable.
Click to expand...
Click to collapse
I updated OP just so it makes more sense
Glad I could be of help
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
jonzey231 said:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
Click to expand...
Click to collapse
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
simms22 said:
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
Click to expand...
Click to collapse
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
jonzey231 said:
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
Click to expand...
Click to collapse
well, then its odd, you should have gotten root after flashing both in recovery.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
I know, right? I'll give it another shot. I'm getting ready to do it now. I'll update in a few minutes when I've finished up.
Edit: Grabbed Elemental from here: http://forum.xda-developers.com/showpost.php?p=61931417&postcount=3921&nocache=1
Updated last night so it should be the absolute latest version. So I'll flash twrp in fastboot, then boot into twrp and flash the kernel first, and then supersu and I should be good to go.
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
jonzey231 said:
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
Click to expand...
Click to collapse
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
It's been in a bootloop for like 5 minutes. It would get the the Android is Starting screen and loan for about 30-40 seconds, then reboot.
Then it would hit the validation screen and reboot.
Then it would boot back to Android is Starting, freeze, and reboot lol
It is very erratic, all of this has been going on without any interference from me. Just letting it sit there trying to work through it's issues.
Then all of a sudden as I was typing "adb reboot-bootloader" the thing boots right into my existing lockscreen haha. So I guess I'll just do my best to not have to reboot this thing in case it wants to have a seizure like that again lol.
simms22 said:
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
Click to expand...
Click to collapse
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
jonzey231 said:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
jonzey231 said:
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
Click to expand...
Click to collapse
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
jonzey231 said:
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
Click to expand...
Click to collapse
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
simms22 said:
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
Click to expand...
Click to collapse
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
jonzey231 said:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
Click to expand...
Click to collapse
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
simms22 said:
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
Click to expand...
Click to collapse
Awesome, I didn't really he'd made a ROM for Preview 2 yet. I'll make a backup and give it a shot, thanks for pointing this out to me.
I'll let you know how it goes as well!
Update: it worked!!! I wiped the system partition and flashed the ROM. It failed the first time so I tried again after mounting the system and now I've got too with system write access!! Spread the word my friend.
Is any one tried to flash j700(F/H/M) series on J700T?
rgazapo said:
Is any one tried to flash j700(F/H/M) series on J700T?
Click to expand...
Click to collapse
Yes I have flashes every single rom. They have incorrect bin and vendor files so they reboot every minute. The old Marshmallow ROMs for the M varient, would stick but u had to flash our J700t kernel ( permissive ) first then it worked. I have 2 new j7 ports almost done. Hang tight I got Some new stuff coming...
fullofhell said:
Yes I have flashes every single rom. They have incorrect bin and vendor files so they reboot every minute. The old Marshmallow ROMs for the M varient, would stick but u had to flash our J700t kernel ( permissive ) first then it worked. I have 2 new j7 ports almost done. Hang tight I got Some new stuff coming...
Click to expand...
Click to collapse
You are my hero, thanks!!!
Yeah I've flashed a few of them. Like he said they bootloop unless you put the j700t kernel.
I've also flashed one of their kernels which successfully installed but wouldn't get past the samsung logo.
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
About
This is Unofficial mod rom for adding tweaks , I will work on a making this full user friendly for mido , plus adding another latest features which are not officially supported to LOS
How To Flash
1.Make a BACKUP of current boot,data and system partition first partition using TWRP.
2. Wipe system,data,dalvik and cache.
3.Flash the ROM.
4.Flash the Gapps.
5.Reboot
Download:
ROM
GAPPS
Credits & Thanks:
LineageOS team
ResurrectionRemix team
crDroid team
And all other open source Devs/Teams I may have missed!
Pipaolo
SamarV
Dhiraj
Sandeep Sethi
Adam Belamri
Good job sir, work fine for me
First of all, many thanks for developing a ROM for this device.
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
facing same problem
me too facing exactly same issue
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7 [/QUOTE]
Phone is stuck at moto logo after flashing the rom
CJ2311 said:
First of all, many thanks for developing a ROM for this device.
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
Click to expand...
Click to collapse
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
ahmadmemon said:
me too facing exactly same issue
As far as feedback can go though : I've tried installing this rom over and over again but without luck.
I tried flashing the rom (with and without gapps) on TWRP 3.1.1 as well as TWRP 3.2.2.0. Every time I get the boot screen (Moto powered by android) with the usual warning about the phone being unlocked, then the warning goes away and the boot screen just hangs there without any indication of anything happening on the screen.
Device : XT1663
Stock ROM : Moto-M_XT1663_S378_180503_ROW Android 7
Click to expand...
Click to collapse
[/QUOTE]
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
Swaraj Kumar said:
Phone is stuck at moto logo after flashing the rom
Click to expand...
Click to collapse
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
blitzfire3 said:
Pls try this version and tell me if u face same issue or not
http://adambelamri.eu/MOTO_M/Rom/Releases/Los/lineage-14.1-20180811-UNOFFICIAL-XT1663.zip
Thanks
Click to expand...
Click to collapse
Tried this version and I have the same problem.
Is there any way we could maybe help? By providing certain files or something?
CJ2311 said:
Tried this version and I have the same problem.
Is there any way we could maybe help? By providing certain files or something?
Click to expand...
Click to collapse
well Look like something happen with the source btw did u try the old version of los?
if not here is the link Los 14.1 Test 1
blitzfire3 said:
well Look like something happen with the source btw did u try the old version of los?
if not here is the link Los 14.1 Test 1
Click to expand...
Click to collapse
I have tried lineage-14.1-20180702-UNOFFICIAL-XT1663.zip, if that's what you're referring to.
CJ2311 said:
I have tried lineage-14.1-20180702-UNOFFICIAL-XT1663.zip, if that's what you're referring to.
Click to expand...
Click to collapse
Try the new one i uploaded yesterday and tell me the result
blitzfire3 said:
Try the new one i uploaded yesterday and tell me the result
Click to expand...
Click to collapse
Currently just flashed that file, and I got past the motorola logo screen, but now I seem to be having a bootloop. I'll leave it be for an hour or so then I'll try to reinstall again if it doesn't work still.
CJ2311 said:
Currently just flashed that file, and I got past the motorola logo screen, but now I seem to be having a bootloop. I'll leave it be for an hour or so then I'll try to reinstall again if it doesn't work still.
Click to expand...
Click to collapse
Did u get any further? Waiting for your feedback.
Yes plz post a review on this ROM
blitzfire3 said:
Try the new one i uploaded yesterday and tell me the result
Click to expand...
Click to collapse
Thapagaurav said:
Did u get any further? Waiting for your feedback.
Click to expand...
Click to collapse
[email protected] said:
Yes plz post a review on this ROM
Click to expand...
Click to collapse
Sadly, I've kept getting a bootloop on the new build no matter what. Tried reinstalling several times, with and without gapps/superSU but no luck.
CJ2311 said:
Sadly, I've kept getting a bootloop on the new build no matter what. Tried reinstalling several times, with and without gapps/superSU but no luck.
Click to expand...
Click to collapse
there is some problem with the rom i will look at it
@CJ2311 thanks for testing and really appreciate the feedbacks. I have a question about your Moto M, are you experiencing the battery drain as well? like once it reaches to 50% or below it'll immediately drain to 2% in just 1-2 minutes or so?
@blitzfire3 thank you so much for your time developing LOS 14.1 as I'm really looking forward to getting it if this battery drain issue won't be addressed as it seems Lenovo/Motorola doesn't plan to anyway...
blitzfire3 said:
there is some problem with the rom i will look at it
Click to expand...
Click to collapse
Any bugs is there in this rom lineage-14.1-20180825-UNOFFICIAL-XT1663.zip ?
SeishiNui18 said:
@CJ2311 thanks for testing and really appreciate the feedbacks. I have a question about your Moto M, are you experiencing the battery drain as well? like once it reaches to 50% or below it'll immediately drain to 2% in just 1-2 minutes or so?
Click to expand...
Click to collapse
Sounds like you might have a defective unit.
Personally for me it's quite the opposite, the phone holds the entire day easily, and I can often make it last 2 days. Whenever I get the battery low warning it'll keep running for quite a while in standby or light use, and even when I get the "battery level critical, phone shutting down in 30 seconds" warning, it only shuts down after 5 minutes or more... D: