Related
I posted this issue some days ago on "XPERIA X8 Q&A" and still i see many posts about these screen cuts in Development threads linked to MiniCM7 based roms. I think these cuts are not related to the rom but to nAa kernel newest version since i had this cuts in CWM recovery with stock rom after installing this kernel.
I don't know if this will work for everyone but on my GingerXperiaRay i fixed the issue by activating boot anymation on CyanogenMod configs 2 days ago and since then i have no screen cuts.
Hope this fixes the issue for you guys too.
I don't have that problem
even with bootanimation off
i have this problem on CWR only
i'm safe
Same here. There isnt a issue for me. You try reflashing the kernel again. If it still gives a error do the following:
1. Back up SD card.
2. Format it.
3. Flash Kernel.
4. Reinstall ROM [ I prefer you use MiniCM only]
5. Hit thanks IF I helped you.
P.S:- While replacing old files of your memory card. Dont copy all of them. As the new kernel cant read the files stored for the stock kernel. Copy only IMPORTANT DATA [ Music, Contacts, Just few apps ]. Dont copy any app already stored on SD card. I suggest you download it again.
New solution,
Flash nAa v08b kernel
Sent from my E15i using xda premium
fixed on nAn 8b
fixed all bugs with screeN on nAa 8b and grafic beter
I have the same problem, i will try flashing NAa 8b
---------- Post added at 10:40 PM ---------- Previous post was at 10:21 PM ----------
It worked, no more screen cuts Nice work from NAa
I recently installed GingerIceJelly custom ROM on my Galaxy Y Duos GT-S6102. It added a boot image (that is displayed even before the recovery menu when I boot in a recovery mode). I later reverted back to my stock ROM, but the boot image still remains. I had thought it was part of the GingerIceJelly ROM, but apparently not. If it is not part of the kernel, where is it?
Is there a way to remove it?
Thanks
Eldho Thomas
Boot.img isn't part of the kernel it's all of it lol boot.img is the kernel
flashing stock Rom via Odin should wipe it
PHONE SLOW CLICK ME?
_____________________________________
"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"
Lol. boot.img is the kernel. The thing you want is the Bootanimaton right? Its in the system/media with the file name of bootanimaton.zip
eldhothomas said:
I recently installed GingerIceJelly custom ROM on my Galaxy Y Duos GT-S6102. It added a boot image (that is displayed even before the recovery menu when I boot in a recovery mode). I later reverted back to my stock ROM, but the boot image still remains. I had thought it was part of the GingerIceJelly ROM, but apparently not. If it is not part of the kernel, where is it?
Is there a way to remove it?
Thanks
Eldho Thomas
Click to expand...
Click to collapse
U talking about yellow pink screen that comes before boot?
Its because of kernel made for the rom..change your kernel and its done..
Sent from my GT-S6102 using xda app-developers app
Thanks guys !
So, when I restore my phone back to the stock Samsung ROM, doesn't it restore back to the old Kernel?
PS: I am talking about the purple-yellow-etc screen that says "GingerIceJelly with compact kernel etc..... Nitu Bhaskar etc." even before the Samsung boot animation.
Thanks
Eldho Thomas
eldhothomas said:
Thanks guys !
So, when I restore my phone back to the stock Samsung ROM, doesn't it restore back to the old Kernel?
PS: I am talking about the purple-yellow-etc screen that says "GingerIceJelly with compact kernel etc..... Nitu Bhaskar etc." even before the Samsung boot animation.
Thanks
Eldho Thomas
Click to expand...
Click to collapse
Yes..just flash another kernel or flash stock rom via odin..and you are done.simple
Sent from my GT-S6102 using xda app-developers app
Need To Change The Kernel
eldhothomas said:
I recently installed GingerIceJelly custom ROM on my Galaxy Y Duos GT-S6102. It added a boot image (that is displayed even before the recovery menu when I boot in a recovery mode). I later reverted back to my stock ROM, but the boot image still remains. I had thought it was part of the GingerIceJelly ROM, but apparently not. If it is not part of the kernel, where is it?
Is there a way to remove it?
Thanks
Eldho Thomas
Click to expand...
Click to collapse
Yes you can remove it for this you have to change the kernel of your phone i would recommend to use iduos 1.2.1 as it is very stable with no bugs
Hope this Helps you.
---------- Post added at 09:33 AM ---------- Previous post was at 09:19 AM ----------
Please Give Solution For The Following Problems :-
1. Bluetooth, Wi-Fi, Data, Wi-Fi Hotspot Not Working Together.
2. Lockscreen Menu Is Of No use There Is No Change In The Lockscreen.
3. Scrolling Is Not Working properly In The Whole UI Need To Swype In The Opposite direction to stop the Scrolling.
4. GIJ Tweak Style Shop BootAnimations, Tweaks AD-HOC.zip Is Not Flashing Says
Error Flashing
(status:0)
5. OTA Updater Not Workig Says "Invalid Rom"
Due To These Problem I Can't say that it is a stable Custom Rom
I Dont't know that these problems are general or are Only happening to My Phone But Please Tell Me The Solutions.
Tech Knowns said:
Yes you can remove it for this you have to change the kernel of your phone i would recommend to use iduos 1.2.1 as it is very stable with no bugs
Hope this Helps you.
---------- Post added at 09:33 AM ---------- Previous post was at 09:19 AM ----------
Please Give Solution For The Following Problems :-
1. Bluetooth, Wi-Fi, Data, Wi-Fi Hotspot Not Working Together.
2. Lockscreen Menu Is Of No use There Is No Change In The Lockscreen.
3. Scrolling Is Not Working properly In The Whole UI Need To Swype In The Opposite direction to stop the Scrolling.
4. GIJ Tweak Style Shop BootAnimations, Tweaks AD-HOC.zip Is Not Flashing Says
Error Flashing
(status:0)
5. OTA Updater Not Workig Says "Invalid Rom"
Due To These Problem I Can't say that it is a stable Custom Rom
I Dont't know that these problems are general or are Only happening to My Phone But Please Tell Me The Solutions.
Click to expand...
Click to collapse
post the same in original thread..
U will get better ans.plus,it would be helpful for other users too
Sent from my GT-S6102 using xda app-developers app
Tech Knowns said:
Yes you can remove it for this you have to change the kernel of your phone i would recommend to use iduos 1.2.1 as it is very stable with no bugs
Hope this Helps you.
---------- Post added at 09:33 AM ---------- Previous post was at 09:19 AM ----------
Please Give Solution For The Following Problems :-
1. Bluetooth, Wi-Fi, Data, Wi-Fi Hotspot Not Working Together.
2. Lockscreen Menu Is Of No use There Is No Change In The Lockscreen.
3. Scrolling Is Not Working properly In The Whole UI Need To Swype In The Opposite direction to stop the Scrolling.
4. GIJ Tweak Style Shop BootAnimations, Tweaks AD-HOC.zip Is Not Flashing Says
Error Flashing
(status:0)
5. OTA Updater Not Workig Says "Invalid Rom"
Due To These Problem I Can't say that it is a stable Custom Rom
I Dont't know that these problems are general or are Only happening to My Phone But Please Tell Me The Solutions.
Click to expand...
Click to collapse
1. I have not seen wifi and data network working together as soon as there is wifi data network is automatically switched off...
2 don't know sorry u can ask the developer
3.i guess it's got something to do with the scrolling hack u can again contact the developer for this..
4. is is usually caused by an incompatible update-binary in edify ZIPs. Replacing it with a compatible one, then re-signing the ZIP, will usually fix this error. Our another way ask the Dev or is not for your phone..
5.probably because you have modified the build. Prop file in system /
:thumbup:
Sent from my GT-S5360 using xda app-developers app
Precision...
Hey,
Can you be bit more precise..We have not tried that GingerIceJelly rom so you should be able to tell the problem clearly maybe uploading an Image will be appreciable.Ok here is what i know that i thought of sharing with you.
When the phone's power is turned on the bios boots the phone to bootloader which Runs the kernel from it.And while the kernel modules are inserted,the phone now loads the rom.
So you now know where the problem is.
yes Download the bootloader and flash it.
Get your odin flashable stock and flash BCMboot.img or some file which only contains bootloader.
If you want to try changing your bootanimation click here
Thanks,
optimus
Tech Knowns said:
Yes you can remove it for this you have to change the kernel of your phone i would recommend to use iduos 1.2.1 as it is very stable with no bugs
Hope this Helps you.
---------- Post added at 09:33 AM ---------- Previous post was at 09:19 AM ----------
Please Give Solution For The Following Problems :-
1. Bluetooth, Wi-Fi, Data, Wi-Fi Hotspot Not Working Together.
2. Lockscreen Menu Is Of No use There Is No Change In The Lockscreen.
3. Scrolling Is Not Working properly In The Whole UI Need To Swype In The Opposite direction to stop the Scrolling.
4. GIJ Tweak Style Shop BootAnimations, Tweaks AD-HOC.zip Is Not Flashing Says
Error Flashing
(status:0)
5. OTA Updater Not Workig Says "Invalid Rom"
Due To These Problem I Can't say that it is a stable Custom Rom
I Dont't know that these problems are general or are Only happening to My Phone But Please Tell Me The Solutions.
Click to expand...
Click to collapse
1. all radio problem will be fixed in ota update about 2 or 3 days again...
2. this uncomplete project
3. this in no bug!!! but NEW SMOOTH SCROLING METHOD by official firmware DXLK2... actually in DXMA1 scroling method back to old.. but i like this scroling mthod. so, i keep this....
4. will be fixed to.... TweakStyleShop update will be deferent file with ROM OTA-UPDATE... you will need update booth of them..
5. its normally... IT FOR squential update features....
because no ID updatefile that matched...dont worry if any update you will received that, so, it not error or bug.,
Editing plat text
You need to decompile framework.har inside that in a folder is a file named platlogo go inside that there is that line edit it compile the jar you are done
Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!
flyingsilverfin said:
Hello,
I'm a little late to the Razr M game, but I just got a device off ebay since it's only about a year old and in great shape and quite cheap :good:
In any case, I've so far managed to unlock the radio for Tmobile in the US (GSM), and root it the device. Unfortunately, I didn't know when i bought it about the inability to unlock the bootloader with OTA from May and beyond, which mine is according to fastboot. I believe I came across the actual number being 98.18.78 somewhere.
So I've been doing a lot of reading, got SafeStrap running, made a stock backup, and am testing on slot1. However, I can't seem to get any CM ROM's running! Most of them 'boot' but then all I get is a blank screen, though I can connect with adb and therefore confirm that it does actually run some CM build.
I'm first of all somewhat confused on what ROM i should be using. I've found several links that should seem like they work, but none have succeeded (all have that halfway functionality that only works in ADB):
http://d-h.st/FgU
http://skrilax.droid-developers.org/cm10.1nightly/razrqcom/index.php?device=xt907
http://goo.im/devs/Hashcode/scorpion_mini/cm10.1
http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907
I found these in various threads on XDA and droidrazr.com. I basically read the entire 55 pages of http://forum.xda-developers.com/showthread.php?t=2012093 and since the link in the first page is dead I tried all the links that came up on the thread, which got a couple of the links in my list above.
Also, I did run across the tip that I had to mount system in SafeStrap to get these working, no success. And what's this thing about having to wipe dalvik and system and cache two or three times??
Basically I'd like the proper, up to date link that should be working, along answer to above question and and other tips!
Thanks!!! I love the phone otherwise it's great
UPDATE:
I did manage to get an CyanogenMod spinning forever startup screen with an ancient rom described here http://www.droidviews.com/install-first-aosp-based-unofficial-cm10-rom-on-motorola-droid-razr-m-xt907/ which appears to have come again from the thread mentioned above. The link is now gone but I have the .zip that I must have snagged right before it disappeared!
Click to expand...
Click to collapse
There is not much.
You will not find much better than Mhous33's dst & my sd swap here : http://forum.xda-developers.com/showthread.php?t=2442384
There is also one at RZR http://www.droidrzr.com/index.php/topic/33740-rom-jb-98163-xt907-rage-m-v10-1232013/
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
There are others but they are not current.
Well, none of the custom ROMs out now will work with SS. Their are some stock based ROMs, one of which was posted by Avi, that will work with SS. There are some older ROMs that were designed for SS and they were built prior to April (when our bootloader was unlocked). You'll have to dig back a couple of page to find them. I know there was SS compatible CM10 in that link you posted, but I don't think the link is active for it anymore. If you decide to run an older SS compatible ROM on your newer system version, you're going to run into kernel issues. Things like the gallery not working and WiFi signal being weak. Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.
Thanks for the response, I'll check those out. Glad to find some up to date roms haha
aviwdoowks said:
Your boot ,which includes the kernel & recovery are locked. All the roms you list use a non stock kernel.
Click to expand...
Click to collapse
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?
RikRong said:
Your best bet right now is to load a stock ROM on slot 1 and start tweaking that with XPosed and enabling Init.d so you can get some performance tweaks going.
Click to expand...
Click to collapse
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error
flyingsilverfin said:
Thanks for the response, I'll check those out. Glad to find some up to date roms haha
This is something I didn't realize/know before, good to know! That would explain some of the problems. May I ask how you know they don't use stock kernels? Just experience in the development process or is there a way to check?
Click to expand...
Click to collapse
Word would get round if they did, but What vzw wants moto to do to a phone is not what cwm wants to do. 4 cyl hi mpg VS racing v8
Same problem with the xt907-98.30.1-deodexed rom:
E: signature verification failed
Not sure what's wrong with BOTH of these?
Sorry, didn't do enough testing. Disabled zip verification and it wrote, just have to see its working!
flyingsilverfin said:
Thanks for the info, I'll have to do some research if aviwdoowks's pointers dont work out! Second day fiddling with this stuff on android so I don't know what XPosed is/what Init.d does (although I think Ubuntu has that file too...)
Also, I tried the DeadCalm SS rom and i get an
E:signature verification failed
error
Click to expand...
Click to collapse
Did you mount system before installed it?
All SS roms need mounting.
My link has steps.
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I think DC is not SS ready.
---------- Post added at 09:18 PM ---------- Previous post was at 09:08 PM ----------
DC flashes the damn skull bootlogo, easy to delete the bootlogo & # out instructions in the updater-script, other things too for a DIY SS rom
---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------
DL my SS deodexed & use it as a templet as to what items need to be taken out.
Root Explorer is all you need.
Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.
flyingsilverfin said:
Thanks for the help and links, I have the deodexed SS version from your link working. I see that it is not a debloated version; is the odexed version debloated?
Also I was originally hoping for a ROM with functionality like Cyanogenmod, but I guess the situation is too specific for that too happen. I might be interested in getting to ROM making/customizing at some point, I did some preliminary reading, I should be able to edit the deoxed SS ROM and then 'stitch it up again' in simplest terms, and it will still work on my device, correct? I feel like editing a ROM would be a great way to learn more about Android/Linux/bootloaders etc before I go to college.
Click to expand...
Click to collapse
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.
aviwdoowks said:
The odexed is DST which means a debloated to the same specs at the Telstra build. The SD swap works on both.
Click to expand...
Click to collapse
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.
flyingsilverfin said:
What is the telstra build? Is that the name of the stock motorola ROM that came with the device? Also I'm guessing SD swap is just a way have the phone treat the SD as internal memory?
Also, any idea if it would be possible or how difficult it would be to modify the ROM you linked me to to turn it into a Cyanogenmod port?
Thanks for all the help
Click to expand...
Click to collapse
Telstra is a carrier for the xt905. There are builds posted in our dev section. Any telstra rom is encrypted & if flashed w/ Rsd or Fastboot will brick an xt907.
Very difficult. Edit impossible.
RikRong said:
Telstra is the Australian firmware, I believe. If you want to port CM, you need to pull from their source. The DST ROM is a stock Moto ROM that's built by the Moto software team. You can't really take that and change it into a CM port, but you can make your own build environment and start building CM.
Click to expand...
Click to collapse
Alright thanks for the info. I was just doing some reading on the Linux Kernel. Since I am stuck with the stock motorola kernel, but this implements all the things I need to make the upper level, platform independent sys calls and other api's, there shouldn't be a need to build a special kernel for a cyanogenmod port, correct? If i port the higher level things everything that is implemented in cyanogenmod should work... am I getting this right? I'm trying to figure out what the OS kernel requirements are.
It's been requested that I create a new thread for this so as not to clog up @milaq's thread.
As some of you may have seen in flintman's Evervolv and milaq's CM threads, there has been a lot of work on the 3.4 kernel for tenderloin. Its a pretty awesome feat to have this running on our good ol tenderloin. =)
The gratitude for this kernel and build needs to be given to almost anyone but me. (Flemmard, flintman, jcsullins, Dorregaray and everyone that came before me on this device (dalingrin, green, and other's I'm sure that I'm missing)). I've had my tenderloin for quite awhile but never really done much with it until recently.
Anyway, without further ado, I present to you nightlies of CM-11.0 for tenderloin with a 3.4 kernel and -caf based HALs. Basically what this means is we'll be running the latest code from codeaurora on our msm8660 tenderloin.
THERE WILL BE BUGS! This thing is not perfect. It is still in active development.
CURRENT BUGZ (in no particular order):
- Bluetooth steals battery, but DOES work (jcsullins) - also sixaxis app doesn't work =(
- Camera is a bit derpy still, major wip, it takes pictures though (Dorregaray)
- Other stuff? Probably, yea
Destructions: PLEASE READ
1. This is a /data/media rom (relevant). What that means is you should be partitioned with a very small 'media' partition and a very large 'data' partition. The benefit of this is that your /sdcard and /data partitions share the big chunk of your usable space, just like any newer phone does these days. Use TPToolbox to achieve the new partition scheme: http://forum.xda-developers.com/showthread.php?t=2756314
2. You'll need a recovery that has both /data/media support and selinux support. Any of the following will work. Flashable via recovery.
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
3. Now you're ready to flash the rom. Downloads here: http://www.invisiblek.org/roms/cm-11.0/tenderloin/
4. Gapps here: http://wiki.cyanogenmod.org/w/Google_Apps
I'd recommend wiping data when coming to this rom or going to a different one (going between milaq's and this should be fine).
These are automatically built on my personal server at home and then uploaded. There may or may not be issues during the build times so don't always expect a fresh build every day. You can follow the automated twitter account here which will spit out a tweet once the build is finished uploading.
Sources:
-Kernel
-Device Tree
-CM Sources (the rest of what's needed)
There are a couple more changes and a couple other repos that are required to build this. Add this stuff to your .repo/local_manifests/roomservice.xml in order to build this yourself (after syncing the cm source of course)
http://pastebin.com/jKAMWM8T
You'll also need to cherry pick this commit from jcsullins: http://review.cyanogenmod.org/#/c/54380
Feel free to fork and fix!
Again -
Thanks to everyone that has contributed to making this rom.
Flemmard, flintman, jcsullins, dalingrin, green, milaq, the entire CM team and I'm sure many others.
Good new year present.
Looking forward to when Bluetooth is working. That and the black boxes were the only thing keeping me off KitKat.
Sent from my TouchPad using XDA Premium 4 mobile app
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
k4ever said:
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
vinukondamahesh said:
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
Click to expand...
Click to collapse
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
k4ever said:
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
No clue. I heard of apps disappearing from the Google Home Launcher, but not getting completely removed or preventing apps from being installed. Is that the launcher you're using? Only remedy I heard from that (Milaq's CM11 thread, somewhere around page 40) was to just readd them from the app drawer.
Best advice is to wait for todays build to get uploaded and see what happens.
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
allstar319 said:
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
Click to expand...
Click to collapse
thank you its working nw
milaq actually has a flashable zip in his thread. that is the easiest. i was on 4.3 went into that recovery, made a backup then flashed the new cwm, rebooted recovery did a full wipe and flashed the rom and gapps and i am up and running. who would have ever thought we would have kitkat on a touchpad. not to mention a 3.x kernel. unreal, thanks for everyones work. Happy New Year
jerryatherton said:
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
Click to expand...
Click to collapse
Oops, I had the wrong image there. Link updated with the cwm =P
EDIT: Also added a flashable zip for it, had trouble downloading milaq's so I made my own =/
Anyone else getting a Core Process failure message when booting to the 01012014 Build?
I went back to the 12312013 build and all appears to be back to normal.
To be clear, I went straight to this build from a fresh CM9 image without booting into Android - ever. Got a second-hand device back from a relative, and pushed it to CM11, so it may have been a result of my own process.
I'll reflash 01012014 and see if the error persists.
--McBean
Really looking forwards to a stable version of this to try. Thanks for the effort.
BillzillaAus said:
Really looking forwards to a stable version of this to try. Thanks for the effort.
Click to expand...
Click to collapse
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
k4ever said:
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
allstar319 said:
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
Click to expand...
Click to collapse
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Click to expand...
Click to collapse
Also, the old kernel was preventing us from having "official" CM builds.
Getting SoD's once I turn the screen off. Tried the old way to fix that by raising the min clock, but that didn't seem to help. Any ideas?
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
The 3.4 kernel, minimally, resolves an issues with the other CM11 builds where the core/stock apps were experiencing "black boxes" which prevented users from reading mail, using the browser to navigate and some other issues. Right off the bat, the new kernel resolves that issue.
--McBean
WARNING: I DON'T MAKE THIS ROM, I ONLY WANT TO SHARE IT BECAUSE THERE ISN'T ANY THREAD ABOUT IT.
THIS ROM IS MADE FOR THE GT-I8200(L/N/Q), NOT THE GT-I8190!!
FEATURES:
•S6 Themed systemUI (status bar, recent apps...)
•S5 themed camera
•S6 themed icons
•AOSP Themed settings
•S6 wallpapers
•S6 Bootanimation
•Rooted
•Etc.....
FULL REVIEWS (from Youtube):
HERE
or HERE
DOWNLOAD
Link of the ROM: https://mega.nz/#!29oxCbgR!t9xZpRrqlTDTprPnXkonaOL68rnuzRB3EdqO3SA7B4I
How to install
•Download the ROM to your phone
•Flash PhilZ or TWRP Recovery (You can find them on this thread)
•Through recovery, make a full backup of your phone (just because if something went wrong during ROM flashing you can restore your phone )
•Wipe data, cache and system
•Install the downloaded ROM
•Enjoy!!
Thanks to:
•Allah SWT
•Probando Android
•arbri zeqollari
•Me
•All those who downloaded the ROM (You?!!)
still has dual sim framework ...
georgedk said:
still has dual sim framework ...
Click to expand...
Click to collapse
The second SIM icon on the status bar is not real, it's only a theme.
i know i tested it
now im installing with adb sideload.. so testing..
---------- Post added at 11:36 PM ---------- Previous post was at 11:11 PM ----------
installed and running
so sms applicaiton crashing but no problem. i will install another sms application.
thank you. very nice and fast ui..
Hahahaha they just took my settings.apk
What is the best Stock rom for a Swedish Sold S3 Mini?, gonna reinstall it and give to grandma
bittin said:
What is the best Stock rom for a Swedish Sold S3 Mini?, gonna reinstall it and give to grandma
Click to expand...
Click to collapse
THE STOCK AND ORIGINAL ROM, no root or mod
V2?
Hello, This ROM on which version of Android is based? Android 5.1 Lollipop?
pickmod said:
Hello, This ROM on which version of Android is based? Android 5.1 Lollipop?
Click to expand...
Click to collapse
4.2.2
pickmod said:
Hello, This ROM on which version of Android is based? Android 5.1 Lollipop?
Click to expand...
Click to collapse
It's based on the stock i8200 ROM (4.2.2)
is this possible to get rid of this second sim icon on the bar?
works on i8200?
gallary is gone worng say stopped how to fix dude
https://youtu.be/SL529tVlVvs
watch this nougat rom for gt-i8200N/L???
pandeyshreedhar said:
watch this nougat rom for gt-i8200N/L???
Click to expand...
Click to collapse
Yep. Used this one myself. It's not really Nougat, though... like all other ROMs for the i8200, this is a modified stock ROM and is still Jellybean 4.2.2, just heavily skinned. That said, it's faster than the stock ROM, offers slightly better battery performance, and is quite stable. Worth looking at.
---------- Post added at 03:37 AM ---------- Previous post was at 02:45 AM ----------
cloudmann said:
Yep. Used this one myself. It's not really Nougat, though... like all other ROMs for the i8200, this is a modified stock ROM and is still Jellybean 4.2.2, just heavily skinned. That said, it's faster than the stock ROM, offers slightly better battery performance, and is quite stable. Worth looking at.
Click to expand...
Click to collapse
So, I put together a complete ZIP file with this exact modified stock ROM. I included everything you need to install it.
Disclaimers: this is your phone and I'm not responsible for what you do with it. I've done this process multiple times with tons of different ROMs, and if you follow the instructions from the included text file I authored, it should work perfectly. I'm not responsible for bricked phones, though I did include files to restore from a soft brick.
Also, I did not author this ROM image... it is a modified stock image (like everything else for the i8200) and is not REALLY Nougat or Lineage OS... it's just heavily skinned to look and act like it. That being said, battery life is noticably improved, speed is increased just a bit, and the ROM is stable.
After downloading, extract all files to a directory and then read my instructions... multiple times... make sure you have your mind wrapped around the process before you commit.
Anyway, the file is HUGE (1.25 GB) and the hosting is absolutely free and absolutely middling in download speeds, so give it some time to download... patience and virtues and whatnot. If this file goes without downloads for thirty days, it will self delete from the hosting server, so if you stumble across this thread at some point in the future and the link is dead, message me. I will EVENTUALLY get the PM and I'll update this thread with a new link once I get a chance to upload the file again.
I included the Custom Nougat ROM image, TWRP 2.7.2.0 for the i8200, a SuperSU ZIP file, Odin 3.07 (which I used), a newer Odin for those who prefer it, the needed Samsung driver install file, and a copy of Philz if you prefer that particular recovery. I also included a stock recovery image in case you have a soft brick occur. Also my detailed, step by step instructions in a text file.
Anyhow, here's the link:
http://www.filehosting.org/file/details/746451/S3-i8200 Custom ROM.zip
thanks for support us and providing roms. I recommended to you to make more nice rom for this gt-i8200N/L/Q.
Orignal firmware is to bad and get problem in battery disconnect in charging.so i use roms which is good and no any problems
Is this rom working in 8200Q?
It should, but I don't have one to verify this.
---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM ----------
I'd recommend making a backup in TWRP before flashing this. If it doesn't work, just restore your old backup. The hardware across all i8200 phones is virtually identical with the exception of things like NFC and LTE... this ROM appears to support all of that by default, so it should, in theory, work with any i8200 revision. Give it a try and let us know.