OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?
That would be great and highly appreciated. :good:
kornelius1982 said:
That would be great and highly appreciated. :good:
Click to expand...
Click to collapse
start from
http://forum.xda-developers.com/sit...pub-2900107662879704:4763122713&ie=ISO-8859-1
ask help from sktjdgns1189 and arter97
enotar said:
OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?
Click to expand...
Click to collapse
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."
Compile a kernel almost all the effort (95)% to port a room.
Here´s the first thing we need to do.
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
I´m downloading kernel source of sm-p901.
Here is the index sm-p900´s kernel sources:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-P90
wulkanat said:
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."
Click to expand...
Click to collapse
Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk
If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device
enotar said:
Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
would be better to use the T900 Version with a existing Kernel (don't know if it works ). Just to have it more simple. If it does not work... we can use the P900 Version
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
Wbdsgnr said:
If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device
Click to expand...
Click to collapse
good idea, I will try to boot with T900 Kernel first (Firmware is downloading right now ), but I will also give the P900 Kernel a try, if the T900 Kernel does not work
Found this in a ROM in SM-P900 Forum:
"If you are on KitKat•Make a EFS backup
•Make a Nandroidbackup.
•Download rom and place on your ExternalSD.
•Flash the Lollipop bootloader before installing the rom ar it won't boot.
Here you find the Lollipop Bootloader and Odin package that you need to install it on your device when in download mode.
If you want to revert back to KitKat rom you need to install the kitkat bootloader! You find it here and you flash it with Odin.
•Full wipe is needed and now you can install the rom."
Maby the Bootloader is the Reason why it does not boot?
I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
enotar said:
I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
already tried it out with a Tab S ROM . And for now, (~10 sec left) i'm on KitKat back.
Did not work. But it was a try... so, black screen, and reboot. Kernel or bootloader? It does not Boot with ValexKernel too, but this is a AOSP kernel. (and yes, I'm back on Kitkat)
Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk
enotar said:
Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I have already a Ubuntu iso, so I will try to install it in VMware Which Kernel? from P900 or T900? I will try the P900, if there is no a reason why not.
I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.
P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk
enotar said:
P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Nice!
Wbdsgnr said:
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.
Click to expand...
Click to collapse
The one who made the TW 5.0.2 ROM for SM-P605 just get it too...
I'm hoping the same that someone will port p900 to p600 as both are 99% identical. @enotar, I think T900 not a Note series Tab and doesn't have S-pen functionality. So, you might wanna try P900 rom.
T900 not a Note series !!!! doesn't have S-pen functionality
alex22280 said:
T900 not a Note series !!!! doesn't have S-pen functionality
Click to expand...
Click to collapse
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk
enotar said:
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
ask for help from sktjdgns1189 ,Alan-B and arter97 (I am use a port 5.0.2 for my P605 from Alan - B)
for kernel ....arter97
Related
Hi to all, ive seen some people tried to make cm10.1 but it didnt boot, so... i thought, maybe not cm10.1, but what about cm10? I can port the rom, but i need people for testing and making the kernel. Is there any tablet with this processor? Anyone interested?
Hello
Sorry my bad english i am from Germany and have the and i can test your cm10 port for you if you want
Gesendet von meinem SM-T210R mit Tapatalk 2
cm10 and testing
i'm willing to test whatever you come up with as long as is doesn't bone my partitions
as for cm10.1 there is a booting rom after a fashion, it goes like this
i stitched it together from two roms work on by other people [gr8nole , go here
http://www.androidfilehost.com/?a=show&w=files&flid=7488 scroll down and look for partially booting cm10
and by chpettit
http://www.androidfilehost.com/?fid=23159073880933175
pull boot.img, updater script, and update binary from gr8nole's partially booting cm10
and drop them into chpettit's [overwrite]
goto recovery backup/wipe/flash and see what it looks like
the flicker won't kill you but the messed up touch might the display is stuck in landscape and touchscreen stuck in potrait
not sure it's useful but it's fun for a few minutes
moonbutt74 said:
i'm willing to test whatever you come up with as long as is doesn't bone my partitions
as for cm10.1 there is a booting rom after a fashion, it goes like this
i stitched it together from two roms work on by other people [gr8nole , go here
http://www.androidfilehost.com/?a=show&w=files&flid=7488 scroll down and look for partially booting cm10
and by chpettit
http://www.androidfilehost.com/?fid=23159073880933175
pull boot.img, updater script, and update binary from gr8nole's partially booting cm10
and drop them into chpettit's [overwrite]
goto recovery backup/wipe/flash and see what it looks like
the flicker won't kill you but the messed up touch might the display is stuck in landscape and touchscreen stuck in potrait
not sure it's useful but it's fun for a few minutes
Click to expand...
Click to collapse
Gr8nole partially booing cm was 10.2 not cm10 so it would not work.
I even tried to port his booting cm10.2 with my phone`s cm10.2 but it couldn't flash
hey
HerroYou said:
Gr8nole partially booing cm was 10.2 not cm10 so it would not work.
I even tried to port his booting cm10.2 with my phone`s cm10.2 but it couldn't flash
Click to expand...
Click to collapse
ok i know the process is abit screwy and unintentionally hackish
i repeated it just to be sure so,
1 this is a extract,repack exercise from gr8nole's partially bootin rom to chpettits attempt for the sm-t210r [lt02wifi]
2 pullt the meta-inf directory in it's entirety and the boot.img from gr8nole's rom [cm10.2]
3 INSERT those INTO chpettit's non-booting cm10.1 rom overwriting meta-inf directory and boot.img
4 in PHILZ'S LATEST CWM FOR lt02wifi http://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi
backup your cuurent daily driver rom select th factory reset/clean to install new rom option
after that install the modified chpettit rom
tip; have two copies of the chpettit rom and rename one test.zip , this will be the one you insert
gr8nole's files jnto and thusly the one you will flash
moonbutt74 said:
ok i know the process is abit screwy and unintentionally hackish
i repeated it just to be sure so,
1 this is a extract,repack exercise from gr8nole's partially bootin rom to chpettits attempt for the sm-t210r [lt02wifi]
2 pullt the meta-inf directory in it's entirety and the boot.img from gr8nole's rom [cm10.2]
3 INSERT those INTO chpettit's non-booting cm10.1 rom overwriting meta-inf directory and boot.img
4 in PHILZ'S LATEST CWM FOR lt02wifi http://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi
backup your cuurent daily driver rom select th factory reset/clean to install new rom option
after that install the modified chpettit rom
tip; have two copies of the chpettit rom and rename one test.zip , this will be the one you insert
gr8nole's files jnto and thusly the one you will flash
Click to expand...
Click to collapse
It will not work, cm10.1 and cm10.2 have different kernels and meta-inf
hey
HerroYou said:
It will not work, cm10.1 and cm10.2 have different kernels and meta-inf
Click to expand...
Click to collapse
i just did it, twice.
the problem's with the end result are as i stated earlier.
moonbutt74 said:
i just did it, twice.
the problem's with the end result are as i stated earlier.
Click to expand...
Click to collapse
Yeah but IT DIDN"T WORK!
hey
HerroYou said:
Yeah but IT DIDN"T WORK!
Click to expand...
Click to collapse
everything i desrcibed to you i have just done again which makes three times, same results
i am not a dev, l believe you said something about wanting to port a rom,
i shared something i discovered with you on a thought that maybe you'd
be able to figure out a solution at least to the display issue.
if you can't get the point that i have with it despite the clearest
description i could possibly give, that's fair, but yelling it doesn't work!
without explaining what you've done is unhelpful.
an afterthought; there's a lot to do with these things that shouldn't be doable but are
channel your inner hacker/pirate if they exist [ohmmm]
moonbutt74 said:
everything i desrcibed to you i have just done again which makes three times, same results
i am not a dev, l believe you said something about wanting to port a rom,
i shared something i discovered with you on a thought that maybe you'd
be able to figure out a solution at least to the display issue.
if you can't get the point that i have with it despite the clearest
description i could possibly give, that's fair, but yelling it doesn't work!
without explaining what you've done is unhelpful.
an afterthought; there's a lot to do with these things that shouldn't be doable but are
channel your inner hacker/pirate if they exist [ohmmm]
Click to expand...
Click to collapse
I was just looking at my old phone kernel source, comparing it to stock and cm10.1 there are already major driver differences. Even with cm10.1 and cm10.2. So your "method" will not work.
hmm
HerroYou said:
I was just looking at my old phone kernel source, comparing it to stock and cm10.1 there are already major driver differences. Even with cm10.1 and cm10.2. So your "method" will not work.
Click to expand...
Click to collapse
now i understand you.
don't waste my time.
Cm 10.1 rom working ? Cm 10.2 ?
SM-T311 cihazımdan Tapatalk kullanılarak gönderildi
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again
Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1
Hy guys, I'm trying to make a patch (from grola v2 ls980 patch and zvg update) that can made every stock based Lollipop rom work on LS980 sprint G2.
I tested it on G2PRO2 v5 port and on Grola/simple rom and it works without the signal drops that other patchs have.
Tested on CloudyG2 3.1 and it boot and seem stable [couple of hours now].
Now cloudy made his own patch so use it not mine.
------------------------------------------------------------------------------------------------------------------------------------
Now the baseband is properly displayed, not unknown.
I'm not responsable of brick, phone explosion, sexually transmitted infections, etc.
Installation
0 do a backup
1 you must be on a bumped TWRP
2 flash kk bootloader
3 reboot recovery
4 wipe
5 flash your choosed LP rom
6 DON'T REBOOT
7 flash the patch
8 flash again your twrp recovery
9 reboot
10 enjoy the rom (especially cloudy's one)
Changelog in post 2
Bugs in post 3
Download link in post 4
Thanks to the original v2 grola patch developer and to LG and Sprint.
Changelog
Changelog
V 1.0
Initial release
V1.1
Deleted
V1.2
Added all the needed system files
Removed recovery.img
Known bug
The back notification led is allways on in GPRO2 rom.
Download link
V 1.0
https://mega.co.nz/#!0p1FkKBB!k1g8_lU_2sznybaG1mkH1bdJLGcjm1zcjQyT3qBSs8o
V1.1
V1.2
https://mega.co.nz/#!lgEjAawK!GRQyW0scteNZ54gFn2YxY2oglcRkJCox9j-s8zdC1B8
ZVE BOOTLOADER
https://mega.co.nz/#!o59iAC6J!DhhmN4krLZkqhoo6g2SDRn9gW3sgg_-Vih9ryxqGXwM
so we can use any d802 rom on ls980 now? or is it just for simple rom
I have tried simple (korean) and GPRO2 v5 final (d802) and them works. So in theory this patch can made every LP stock based rom LS980 compatible.
_____________________________________Read more write less and be smart
Nice Job ! Any way I can help ?
gaurangbhartia said:
Nice Job ! Any way I can help ?
Click to expand...
Click to collapse
Thank you! If you want you can test the patch on some roms and give me feedbacks. I want to understand the differences in gps and led between the variants, so we can fix everything on every rom.
_____________________________________Read more write less and be smart
So this is ls980 boot loader for zve. I believe I can find the right commands to pull laf partition and kernel to bump. So we can get TWRP on the LS980 or at least I understand that is the necessity.
siggey said:
Thank you! If you want you can test the patch on some roms and give me feedbacks. I want to understand the differences in gps and led between the variants, so we can fix everything on every rom.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Will do...Let me know which rom you want me to test it on .. Shall I try it on Cloudy's Lollipop rom ?
Btw did you try renaming the product/model lines in the build.prop, to ls980,if not the roms will use the specified d805 or w/e propietary blobs. im not to sure if the lg g2's gps modules are cross compatible with the different models. But i would try this, this way it uses our propietary blobs that you included in patch(system/lib/modules). btw the recovery.img you included in the patch is that the stock recovery, or twrp bumped?
siulmagic said:
Btw did you try renaming the product/model lines in the build.prop, to ls980,if not the roms will use the specified d805 or w/e propietary blobs. im not to sure if the lg g2's gps modules are cross compatible with the different models. But i would try this, this way it uses our propietary blobs that you included in patch(system/lib/modules). btw the recovery.img you included in the patch is that the stock recovery, or twrp bumped?
Click to expand...
Click to collapse
Same goes with nfc. ls980 uses an entirely different chip then the other models.
gaurangbhartia said:
Will do...Let me know which rom you want me to test it on .. Shall I try it on Cloudy's Lollipop rom ?
Click to expand...
Click to collapse
Yesssssssss
_____________________________________Read more write less and be smart
siulmagic said:
Btw did you try renaming the product/model lines in the build.prop, to ls980,if not the roms will use the specified d805 or w/e propietary blobs. im not to sure if the lg g2's gps modules are cross compatible with the different models. But i would try this, this way it uses our propietary blobs that you included in patch(system/lib/modules). btw the recovery.img you included in the patch is that the stock recovery, or twrp bumped?
Click to expand...
Click to collapse
Bumped
_____________________________________Read more write less and be smart
tabp0le said:
Same goes with nfc. ls980 uses an entirely different chip then the other models.
Click to expand...
Click to collapse
hey have u sim unlocked in ZVG? or r u using sprint network?
kadadan said:
hey have u sim unlocked in ZVG? or r u using sprint network?
Click to expand...
Click to collapse
I'm on Sprint.
siggey said:
Yesssssssss
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Tried it... The rom itself doesnt flash properly. I think this is incompatible version due to cloudy's scripts. End Result : System & Data deleted and the phone reboots back to recovery.
imho, we need to update the original zip made by cloudy for his rom.
Do you think it'll work if i use your patch, flash a rom based on official lp for d802, and use the bluecyclon kernel?
zach_95 said:
Do you think it'll work if i use your patch, flash a rom based on official lp for d802, and use the bluecyclon kernel?
Click to expand...
Click to collapse
I think not, if I remember well is a d802 kernel, you need an ls980 kernel.
_____________________________________Read more write less and be smart
gaurangbhartia said:
Tried it... The rom itself doesnt flash properly. I think this is incompatible version due to cloudy's scripts. End Result : System & Data deleted and the phone reboots back to recovery.
imho, we need to update the original zip made by cloudy for his rom.
Click to expand...
Click to collapse
Are you sure that the rom is downloaded property? Md5 ok? Some time ago I tried flash it with another patch, and except big signal drop issues the rom works. Now I cant but when is possible I download it and try by myself.
_____________________________________Read more write less and be smart
I have tried several times but I'm not able to install xposed framework. my last attempt lead my sm-t705 to a bootloop, can anyone explain the steps here? I'm using tw 5.0.2, rooted, twrp recovery, up in the air 1.7 kernel.
Make sure your rom is deodexed then Install this zip via twrp:
http://forum.xda-developers.com/attachment.php?attachmentid=3388977&d=1435913710
Then install the Alpha 4 apk:
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
That's it, reboot and you should have xposed.
ashyx said:
Make sure your rom is deodexed then Install this zip via twrp:
http://forum.xda-developers.com/attachment.php?attachmentid=3388977&d=1435913710
Then install the Alpha 4 apk:
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
That's it, reboot and you should have xposed.
Click to expand...
Click to collapse
thanks ashyxs, my rom is not deodexed, so it was the problem in my previous attempts.
now, how shoud I deodex my rom? Its the official rom from samsung and I don't want to use custom.
thanks again
amirz2ir said:
thanks ashyxs, my rom is not deodexed, so it was the problem in my previous attempts.
now, how shoud I deodex my rom? Its the official rom from samsung and I don't want to use custom.
thanks again
Click to expand...
Click to collapse
What you said doesn't make sense, if you modify a stock rom it becomes custom.
If you root, deodex and install xposed then your stock rom becomes custom.
You need to do all 3 to make it work.
I would suggest saving yourself some hassle and installing the rom below, it is practically a stock lollipop rom, which is deodexed and rooted. All you need do is install xposed.
https://mega.nz/#!E58E1RSR!UMzKgt382bO32s_Qvso5fW445aI3_8EemkVuFK4hXRo
ashyx said:
I would suggest saving yourself some hassle and installing the rom below, it is practically a stock lollipop rom, which is deodexed and rooted. All you need do is install xposed.
Click to expand...
Click to collapse
thanks Ashyx,
what I meant by costume rom was that I want a clean rom with out any unnecessary modifications.
who is the developer of this rom? I've never seen this rom before except for t800.
amirz2ir said:
thanks Ashyx,
what I meant by costume rom was that I want a clean rom with out any unnecessary modifications.
who is the developer of this rom? I've never seen this rom before except for t800.
Click to expand...
Click to collapse
Developer is not-i called sweetrom. Its a very good stable rom, hardly anything removed except for a few bloat apps.
@ashyx I am trying to get xposed on T800, do the files you attached work too or should I get something else? Can you refer me to the xposed thread you're getting the files from? I have xposed on my OPO with Blisspop but trying to get it on a Tab S T800.
vurtomatic said:
@ashyx I am trying to get xposed on T800, do the files you attached work too or should I get something else? Can you refer me to the xposed thread you're getting the files from? I have xposed on my OPO with Blisspop but trying to get it on a Tab S T800.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpo...g-lollipop-t3113463/post60857320#post60857320
I know this is an old thread but I need some help. I'm on the latest version of stock TouchWiz and I've gone through the deodexing process but I still cannot get Xposed installed. It sticks at the Samsung boot animation after flashing any and all zip files that TWRP allows me to flash.
noxarcana said:
I know this is an old thread but I need some help. I'm on the latest version of stock TouchWiz and I've gone through the deodexing process but I still cannot get Xposed installed. It sticks at the Samsung boot animation after flashing any and all zip files that TWRP allows me to flash.
Click to expand...
Click to collapse
You need to flash the latest arter97 build.
Does it boot after deodexing without xposed?
ashyx said:
You need to flash the latest arter97 build.
Does it boot after deodexing without xposed?
Click to expand...
Click to collapse
I've flashed every version of arter97's builds that said sdk21. I'll try again, and yes, it's booting just fine deodexed.
EDIT: "As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version." Because of that line there, I never tried flashing that particular version. Until now. It worked and finally booted up completely except no modules are showing up in the downloads section.
EDIT 2: Simply reinstalled the Xposed apk and the download section was populated.
Sent from my SM-T700 using Tapatalk
Today when I flashed a zip on stock, deodexed ROM in Flashfire my SM-T700 get bootlop another time... :/ I don't want to trip a KNOX flag.. any ideas?
noxarcana said:
I've flashed every version of arter97's builds that said sdk21. I'll try again, and yes, it's booting just fine deodexed.
EDIT: "As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version." Because of that line there, I never tried flashing that particular version. Until now. It worked and finally booted up completely except no modules are showing up in the downloads section.
EDIT 2: Simply reinstalled the Xposed apk and the download section was populated.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
Pretty much all Samsung devices running LL use the requestConcurrentGC version.
The latest versions will do a device check before installing anyway.
ashyx said:
Make sure your rom is deodexed then Install this zip via twrp:
http://forum.xda-developers.com/attachment.php?attachmentid=3388977&d=1435913710
Then install the Alpha 4 apk:
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
That's it, reboot and you should have xposed.
Click to expand...
Click to collapse
Would you happen to know the framework/APK I need for a Tab A T350 on 5.0 SDK21 ARM downloaded and tried what i thought was correct missed the section about samsung stock roms and bootloop luckly i put the uninstaller and was able to get back to twrp
you mentioned to make sure the rom is deodexed? lost there...is that something that needs to be done on stock rom?
Thanks
Denverfan9 said:
Would you happen to know the framework/APK I need for a Tab A T350 on 5.0 SDK21 ARM downloaded and tried what i thought was correct missed the section about samsung stock roms and bootloop luckly i put the uninstaller and was able to get back to twrp
you mentioned to make sure the rom is deodexed? lost there...is that something that needs to be done on stock rom?
Thanks
Click to expand...
Click to collapse
Why don't you update it to mm then install wanam xposed build. Saves all the hassle of deodex ing.
ashyx said:
Why don't you update it to mm then install wanam xposed build. Saves all the hassle of deodex ing.
Click to expand...
Click to collapse
there is no 5.1/6.0 stock rom for T807.
How to deodex 5.0.2 rom? is there a tutorial?
thanks.
radwaste said:
there is no 5.1/6.0 stock rom for T807.
How to deodex 5.0.2 rom? is there a tutorial?
thanks.
Click to expand...
Click to collapse
You can save yourself some hassle there are some great deodexed roms in the development section.
If you still want Xposed for stock check out the Arter97 thread for the latest modified Xposed. It has been patched to no longer require deodexing.
ashyx said:
You can save yourself some hassle there are some great deodexed roms in the development section.
If you still want Xposed for stock check out the Arter97 thread for the latest modified Xposed. It has been patched to no longer require deodexing.
Click to expand...
Click to collapse
Thanks. I saw arter97's thread.
but in the first post, the quote is emphasized. I am note sure someone try it on odexed stock rom.
/* Prerequisite */
Due to my skills limitation, only deodex'ed ROMs are supported for now.
For more explanations, checkout post 2.
/* Supported firmwares */
Every ARMv7(32-bit) Samsung Lollipop Android 5.0 deodex'ed firmware should work.
But please note that I have tested this only on Galaxy S4, Note 3 and S5.
Click to expand...
Click to collapse
Read on to the recent posts there's been development since then.
http://forum.xda-developers.com/gra...posed-stock-lollipop-5-0-2-to-deodex-t3391599
This ia ancient news, I think exposed killed my knox?, I thought it said it could not install because if it, it asked me if i wanted to disable knox so it could install, I said yes and knox was killed, this was over a year ago and i was on kitkat, is this correct.
Killing knox was the best thing for me once i realised it, no more worrying about killing it any-more, my 2 year warranty is almost out, and i have had no problems with my T800 10.5"
John.