Related
Right guy's,
I was asked to start this thread by Doomlord to see how many others are having problems flashing cm7 roms that contain the custom kernel.
When i flash the recent cm7 roms with k006 as soon as my screen times out or i switch it off with the power button(quick press)the phone goes into re-boot, it does not do it with the usb connected and my phone does not do it on any other rom even the cm7 that uses stock kernel.
I have tried everything i can think off to fix this issue from flashing repair with seus to using a brand new sdcard with just the cm7 update on to flash, i have run out of ideas, Doolord seems to think it is hardware related, please post if you are experiencing this problem, i am not concerned about wlod, this is a seperate problem.
When you post can you say which rom you have flashed and also which kernel, thanks in advance for your help, hopefully we can get this sorted.:
UPDATE..... THE LINK IS FOR THE BEST SOLUTION FOUND BY 9LUKAS5, HE HAS MADE A FLASHABLE ZIP TO SORT MINILOADER ISSUES OUT, SEE POST 28, PLEASE READ HIS OP AND GIVE THANKS.
http://forum.xda-developers.com/showthread.php?t=1046609
running J's latest CM7 v018 k006 on an X10a and never had this problem
I have had this problem to , on an erlier custom kernel with cm7, i dont use cm7 anymore so cant say if i should have this problem now but i know a bunch of People have reported the same issue in the Swedish forum www.swedroid.se that the phone reboots when you put the phone to sleep. With cm7 kernel 006.
Xperia™
Nothing is True, Everything is Permitted!
Xperia84 said:
I have had this problem to , on an erlier custom kernel with cm7, i dont use cm7 anymore so cant say if i should have this problem now but i know a bunch of People have reported the same issue in the Swedish forum www.swedroid.se that the phone reboots when you put the phone to sleep. With cm7 kernel 006.
Xperia™
Nothing is True, Everything is Permitted!
Click to expand...
Click to collapse
Thanks for the info xperia, i think it may be down to k006, the thing is why do some have the problem and others don't?
Sent from my X10 using XDA App
Hey smartgardens iv just had an idea cant beleive i didnt think of this before! Have tried messing with settings on set cpu? I might be worth creating a screen off profile and have 384 as maximum scaling and 245 as the lowest or even perhaps raise the maximum up some more. Perhaps your processor just isnt getting enough juice!
Sent from my Full Android on x10 using XDA Premium App
The Gingerbread Man said:
Hey smartgardens iv just had an idea cant beleive i didnt think of this before! Have tried messing with settings on set cpu? I might be worth creating a screen off profile and have 384 as maximum scaling and 245 as the lowest or even perhaps raise the maximum up some more. Perhaps your processor just isnt getting enough juice!
Sent from my Full Android on x10 using XDA Premium App
Click to expand...
Click to collapse
Hi Steve,
That's a great idea buddy,I will try that later when i get home from work, what you describe is just what may be happening, thanks for the help.
Sent from my X10 using XDA App
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
tremendouz said:
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
Click to expand...
Click to collapse
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Iv tried doing data restores from v17 to v18 and get md5 mismatch even though iv not touched the file name.
Sent from my Full Android on x10 using XDA Premium App
The Gingerbread Man said:
Iv tried doing data restores from v17 to v18 and get md5 mismatch even though iv not touched the file name.
Sent from my Full Android on x10 using XDA Premium App
Click to expand...
Click to collapse
Once before I've had a backup that had the same problem, I couldn't even do a complete restore from that backup. There is probably something wrong with the backup that's causing the problem.
I managed to do a Data restore from J013 to J018.
GreatBigDog said:
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Click to expand...
Click to collapse
sounds promising, ill give it a shot now, even if i was about to install it with stock right now
edit: i cant install the stock one, cause when i flash stock kernel chargemon doomlord provided for me i stuck on se logo
what strange is, that when i leave my phone alone it doesnt reboot, but till i use it a few seconds "reboot" 2-3 times, then im in system again and if i leave it "no reboot",
maybe someone can post how i can delete the following from system/bin/chargemon via pc, adb
Code:
umount /cache
umount /sdcard
umount /cdrom
umount /data/DxDrm/fuse
killall -9 DxDrmServerIpc
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot.img > /proc/splboot/boot_img
echo > /proc/splboot/boot
tremendouz said:
i havent even time to install an app before i get wlod, so cant be setcpu
and i had the same with k005 cm7 rom, and with k006 on miui-formels 2.2,
thanks for thread, i read your pm just few min's ago
Click to expand...
Click to collapse
@tremedouz
Hi Bro,
Doomlord said you was having the same problems, i felt like giving up, no matter what i did the same outcome, anyway hopefully we can sort it out, let us know how you get on with set cpu.
GreatBigDog said:
Just a thought, it could be that your CPU can't handle the OC/UV of K006. Try doing a clean install with one of J's stock builds and then install set cpu on that. Configure set cpu to "On Demand", Max cpu to 998 and then enable "On Boot"
Boot into XRecovery, backup the ROM then flash J018. If you then do an advanced restore of the Data only from the backup you should end up with Set CPU installed and set to run on boot.
Click to expand...
Click to collapse
@Greatbigdog
Thanks for your advice, i have had a try of putting the setting to performence in cyanogen settings but it gave me cyanogen setting error message flashing up once the phone re-booted.
The thing is with vo17 stock my phone runs nice, i have flashed over that but got the same result, i have never tried setcpu, i will try your way later though and post back, thanks buddy.
guys some custom kernels (especially the ones ment for CM7) come with RAMDISKs integrated into the custom kernel and there is no seperate ramdisk available in /system...
so when u skip custom kernel booting the intended ramdisk is not executed and the necessary init scripts are never run... that could be the reason why some users (with CM7) are getting stuck when not using custom kernel for booting...
though the CM7 releases marked STOCK kernel should work... but even if those one are having the same issue then we need to search for another probable cause of the problem...
DooMLoRD said:
guys some custom kernels (especially the ones ment for CM7) come with RAMDISKs integrated into the custom kernel and there is no seperate ramdisk available in /system...
so when u skip custom kernel booting the intended ramdisk is not executed and the necessary init scripts are never run... that could be the reason why some users (with CM7) are getting stuck when not using custom kernel for booting...
though the CM7 releases marked STOCK kernel should work... but even if those one are having the same issue then we need to search for another probable cause of the problem...
Click to expand...
Click to collapse
Hi Doomlord,
I have ran both zips that either provided boot with custom kernal/boot with stock kernal, the last time i used the latter my phone never booted, could this have done something in my partition on my phone?, other than that is the ram disk you are talking about in system/bin ramdisk tar, if so i will have a look.
What about the solution using setcpu, i thought the idea was right thats why the screen switches off and does not when usb is connected.
EDIT... Ok just started testing with setcpu settings/add profile, still the same issue, will activating perflock disabler do any harm?
EDIT... maybe you are right about ramdisk as i have not got one showing in system/bin
EDIT... I have now stopped the phone re-booting by flashing the 2 zips below, custom kernal is now showing in my about phone the only thing is i have wifi error, at least i have got somewhere with cm7 v018, the thing is what has this added to my phone to stop the re-boots?
To get wifi working i have tried the following with no luck, using root explorer copy and pasted from update v018 the kernal,module folder and the chargemon, the phone is still stable though and no re-boots, hope somebody now can work out what is the problem.
Had this problem once when I had the v018 stable and Gapps installed.The phone reboot and the problem didn't come back afterwards
Ok Guys i have finally fixed my phone, i have just flashed j's v19 with custom kernel k007, as soon as the screen went off it went into re-boot mode, this time i flashed j's provided bb52 using the latest flash tool, you have to create a bundle first, i flashed this bb 4 times in a row without turning on the phone, just pull the battery out, i turned the phone on and 30 minutes now without 1 reboot, hope this helps those who have been having the same trouble.
I have the same problem. Created a flash file with Js baseband in the flash tool.
Flashed it, had this problem. Smartgardens says we should flash this several times, but i cant see how that has any effect tbh?!
superleeds27 said:
I have the same problem. Created a flash file with Js baseband in the flash tool.
Flashed it, had this problem. Smartgardens says we should flash this several times, but i cant see how that has any effect tbh?![/Q
Well why don't you try it and post back, whats the point in starting a thread to help if you don't help yourself, i could not use the custum kernal either, as soon as i fladhed v019 k007this morning i had the same problem as you, doing what i posted sorted it.
Click to expand...
Click to collapse
smartgardens said:
Right guy's,
I was asked to start this thread by Doomlord to see how many others are having problems flashing cm7 roms that contain the custom kernel.
When i flash the recent cm7 roms with k006 as soon as my screen times out or i switch it off with the power button(quick press)the phone goes into re-boot, it does not do it with the usb connected and my phone does not do it on any other rom even the cm7 that uses stock kernel.
I have tried everything i can think off to fix this issue from flashing repair with seus to using a brand new sdcard with just the cm7 update on to flash, i have run out of ideas, Doolord seems to think it is hardware related, please post if you are experiencing this problem, i am not concerned about wlod, this is a seperate problem.
When you post can you say which rom you have flashed and also which kernel, thanks in advance for your help, hopefully we can get this sorted.
Click to expand...
Click to collapse
you have to use the miniloader and the splboot.ko from z's incall volume fix kernel to fix that problem
How do we use it, where do we put it etc?
Ok, so here's the deal.
After I updated my s3 to Jelly Bean, the following problem started to appear:
Sometimes when WiFi turns off either manually or automatically (I have Tasker which turns off WiFi when screen goes off), WiFi gets stuck at "Turning off..." and doesn't react on any actions.
The switcher gets greyed out and I can do nothing about it. The only way to troubleshot it is to restart the device. Once restarted, everything works fine, but, as you already guessed, it works not for too long. =)
It all depends how lucky I'm. Sometimes the phone can work the whole day without causing the glitch, when I'm not that lucky I have to restart the phone a couple of times during the day. <- really annoying.
The phone is rooted with Galaxy S3 Toolkit by flashing an insecure boot image.
I tried to do factory reset but problem still remained.
I have attached a few screenshots as a proof as well as a screenshot showcasing my phone's firmware specs.
Any ideas or help will be appreciated.
I would blame Tasker try uninstalling and test .
jje
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
Thanks for the reply. But it seems like this is not the problem with Tasker. As I stated in my previous post, I did factory reset my phone and the problem still remained, though no third-party apps were installed other than those that came stock.
I can reproduce the bug very easily: all I need to do is to turn my WiFi on using the icon under notifications bar and then, once it gets turned on, quickly tap the icon again to turn WiFi off. At that point WiFi gets stuck.
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
starfish_001 said:
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
Click to expand...
Click to collapse
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Domovik said:
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Click to expand...
Click to collapse
excellent - pleasure to help
starfish_001 said:
excellent - pleasure to help
Click to expand...
Click to collapse
What rom are you using, i want also to fix this. Thank you
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
NVM: Just download and flash Siyah. Probably the easiest fix.
3dawg said:
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
Click to expand...
Click to collapse
Nope, flashing kernel will no impact your data.
3dawg said:
NVM: Just download and flash Siyah. Probably the easiest fix.
Click to expand...
Click to collapse
I don't know about Siyah - I simply took a stock kernel, prepared it with the toolkit and flashed it with Odin. This was pretty easy and it worked.
Hope this post helps.
Hey guys,
having a trouble for the last couple weeks.
about 5-6 times a day, with no apparent reason, nor something specific i'm doing.
my phone suddenly freezes and the screen goes black, and the notifications led goes blue (not blinking, permanent blue).
only way out of this is long pressing the power button, and the phone goes back on, as if it was turned off.
tried to find out the source of the problem but with no luck.
i'm using
GT-i9300 S3
Rom: cfDroid v13.1 - based on XXEMA2 (4.1.2 android)
Kernel: Perseus alpha 33 (the latest)
Modem: DXELK1
Mods: JKay, acid soundmod, and some other that comes with cfDroid rom
Anyway to pin point the problem and take care of it without having to fully wipe and install a fresh rom?
if you need any more details please ask and i'll post.
Thanks
Are you undervolting the cpu?
No i dont
Sent from my GT-I9300 using xda app-developers app
Re-flash ROM you're using, wipe cache and Dalvik only, if still no improvement change kernel.
Sent from my GT-I9305 using xda app-developers app
i have the same problem. wiping dalvik cache and cache doesnt fix that problem.
Rom: Omega Rom v43
Kernel: Perseus 33.2
currently im switching over to yank and report back, if the problem is gone.
Hey, please update if it is kernel related.
i want to know this before re-flashing the rom
Thanks!
i'm running yank since 2h and the problem is gone... please test this and report back, so we can send Andrei a message.
I had the same problem maybe you have bad blocks there is another thread having the same problem they have a solution in page 7
Sent from my GT-I9300 using Tapatalk 2
Can you please post the link to the thread?
Edit: did you mean this?
dontobi said:
i'm running yank since 2h and the problem is gone... please test this and report back, so we can send Andrei a message.
Click to expand...
Click to collapse
mmm i don't know whats happaned but for the last 24 hr the problem didn't occur again.
i didn't change anything, not the kernel also.
waiting to see if its happens again..
Same.
Hi there.
I got a very similar problem.
Screen freezes and turns black.
I ran an continues kernel output and saw a mmc action, but i removed the card before i booted up.
(See pastebin below for kernel log)
And besides the screen is black and the device isn't responding, the kernel is still active and running.
First my specs:
Model: GT-I9300
Android: 4.1.2 (latest Stock)
Base: I9300BUEMA1
Stock-Kernel: 3.0.31-919627 [email protected] #1 SMP PREEMPT
Build: JZO54K.I9300XXEMR2
Modifications:
TWRP Recovery (2.3.3.0-GTI9300)
SuperSU (0.99)
Busybox (BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT))
My kernel log:
pastebin.com/hRSpzu0D
I hope somebody is more kernel knowledge can take a look at the paste.
Thanks in advance.
Ok too early to be glad.
the problem is back, only now its less frequent, and the device simply turns off.
no blue led.
Now trying to flash Yanks kernel and will report back in a day.
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
jaidev.s said:
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
Thank you but i didn't have the problem with custom roms my friend
it started couple weeks back.
i'm running custom roms from the day i've got my S3.
thinking about that option as last resort :good:
jaidev.s said:
Why don't you try stock Rom and see!
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
I am on stock. I only added root to be able to see the kernel log.
So it appears to me it isn't really rom related. More like 'something in 4.1.2'.
I wish i could put my finger on it.
Regards.
edit:
Maybe we should start to compare the hardware components?
maybe I solved that.
xenonr said:
I am on stock. I only added root to be able to see the kernel log.
So it appears to me it isn't really rom related. More like 'something in 4.1.2'.
I wish i could put my finger on it.
Regards.
edit:
Maybe we should start to compare the hardware components?
Click to expand...
Click to collapse
There was some user reported that problem the last few days...
I had a similar issue, opened a thread yesterday, followed after Slaphead20 advice and make a factory reset.
what i've done was:
factory reset, cache delet from the recovery mode.
flashed and old rom, let kies do the upgrade.
(backed up through myback up) and re-install only what I really needed.
now the phone seem to be running much faster, no lag at all.
i'm still waiting to see if it's freeze.
Still, I think it a software related since so many users start feel those freezes at the same time, it might be some bug in the last update.
oravi said:
There was some user reported that problem the last few days...
I had a similar issue, opened a thread yesterday, followed after Slaphead20 advice and make a factory reset.
what i've done was:
factory reset, cache delet from the recovery mode.
flashed and old rom, let kies do the upgrade.
(backed up through myback up) and re-install only what I really needed.
now the phone seem to be running much faster, no lag at all.
i'm still waiting to see if it's freeze.
Still, I think it a software related since so many users start feel those freezes at the same time, it might be some bug in the last update.
Click to expand...
Click to collapse
Could you please state how far you downgraded?
I willing to try your aproach and want to be as close as possible to your setup.
Thanks.
xenonr said:
Could you please state how far you downgraded?
I willing to try your aproach and want to be as close as possible to your setup.
Thanks.
Click to expand...
Click to collapse
i've downgrade to the I9300XXDLJ4 (uk rom) firmware- as far as I remembered it was the first JB firmware.
I didn't wand to go back to ICS cause I heard it makes problem to downgrade from JB to ICS- I don't know if that right or not.
tell me if it helped you..
Let's give it a shoot
oravi said:
i've downgrade to the I9300XXDLJ4 (uk rom) firmware- as far as I remembered it was the first JB firmware.
I didn't wand to go back to ICS cause I heard it makes problem to downgrade from JB to ICS- I don't know if that right or not.
tell me if it helped you..
Click to expand...
Click to collapse
Thanks for the info. Here we go:
Code:
Start up recovery mode. (TWR v2.3.3.0)
Recovery: Wipe -> Factory Reset
Wipe -> Cache (already included in factory reset, but to be safe)
Reboot -> Power Off
Start up download mode.
Start up Odin.
Downgrade to: 4.1.1 PDA:I9300XXDLIH CSC:I9300VFGDLJ1 (Germany-VD2)
Start up Android 4.1.1.
System failed to boot up.
Start up stock recovery.
Wipe data/factory reset
Wipe cache partition
Reboot system now
Start up Android 4.1.1.
Start up Kies (v2.5.2.13021_10)
Connect Phone to USB.
Kies auto suggests: PDA:MR2 PHONE:MA1 CSC:MA3 (VD2) -> Update
"Proceed without saving"
"Start upgrade"
Disconnect USB.
Wait for startup Android 4.1.2.
Connect Phone to USB.
Final state: PDA:I9300XXEMR2 PHONE:I9300BUEMA1
I just configured my google account and two WLANs. Nothing else yet.
Will report back tomorrow.
---------- Post added at 02:33 PM ---------- Previous post was at 02:17 PM ----------
xenonr said:
I just configured my google account and two WLANs. Nothing else yet.
Will report back tomorrow.
Click to expand...
Click to collapse
Already crashed and burned. Tried to open YouTube.
Saw the "Introduction screen".
Wanted to clear the notifications so pulled down the notification bar.
Pressed "Clear" (don't know what the english text is there).
And freezed. No response at all.
Back to square one! :crying:
OK after running yank555 kernel for couple of days,
the problem still occurs, only now its more rare (1-2 times a day)
and now no led blinking in blue - the device turns off completely
Here is the first Cyanogenmod for P769. Big thanks to CLEMSYN (from tegra) for helping me develop this. Also to mikegabinsky for helping me with the camera.
Please do the following instructions before FLASHING
http://forum.xda-developers.com/showthread.php?t=2198114
Warning: The procedure is not easy.... You've been warned
##########################################################################
May 22, 2013
Latest compilation on May 19, 2003 from CM10.1 source. Kernel changes are the same. Here is the link
https://www.dropbox.com/s/d52icjavb1e9pvh/cm-10.1-20130519-UNOFFICIAL-p760.zip
##########################################################################
May 4, 2013
Here are the changes
1. Latest sync from cyanogen
2. Removed all NFC stuff in the kernel and in building the ROM
https://www.dropbox.com/s/vq8ry9hftdcxcd2/cm-10.1-20130504-UNOFFICIAL-p769.zip
##########################################################################
APRIL 15, 2013
Latest ROM which fixes low audio in CM 10.1 and includes memory swap and latest OC kernel with 500 GPU
https://www.dropbox.com/s/8gr9x8833c3iree/cm-10.1-20130415-UNOFFICIAL-p760.zip
##########################################################################
APRIL 14, 2013
Here is the latest ROM with latest OC kernel with 500GPU. This includes memory swap.
http://db.tt/Zx5BcKBD
############################################################################
APRIL 14, 2013
OK latest update... I got the kernel up to 1.4ghz (default at boot is 1 ghz) and the GPU to over 500mhz !!!! Here are the changes.
1. Wifi voltage decreased from 1.8 to 1.7mv
2. Default boot voltage will be at 1.0ghz then you have to use an app to OC to 1.2, 1.3 or 1.4.
3. GPU increased to over 500 mhz !!! Results in Taiji Benchmarks are up to 19.53 fps (it was at 15.73 fps at 384).
Default Voltages are as follows:
200mhz - 850mv
300mhz - 950mv
600mhz - 1140mv
800mhz - 1200mv
1000 - 1300mv
1200 - 1300mv
1300 - 1375mv
1400 - 1387 mv
Here is the link
http://db.tt/NNwVuqKY
####################################################################################3
April 13, 2013
Latest KERNEL with Super Undervolting. This is just a kernel with a boot image that can be flashed over the current ROM.
Here are the changes
200mhz - 850mv
300mhz - 950mv
600mhz - 1140mv
800mhz - 1200mv
1000 - 1300mv
1200 - 1300mv
Here is the link
https://www.dropbox.com/s/gq69h28a1mj33ar/P769SuperUCwithOC.zip
Just in case that don't work for you here is the original one
https://www.dropbox.com/s/24fy31ao9vg9s8g/OriginalCWMwithOC.zip
######################################################################################
This will basically turn the p769 to p760 with the appropriate mods to enable proper function of the p769.
######################################################################################
NEW BUILD WITH OVERCLOCK and UNDERVOLT
GPU Overclocked to 384 (from 300)
Added 1.2 ghz speed in kernel
1200 - 1375 mv
1000 - 1350 mv
800 - 1291 mv
600 - 1200 mv
300 - 950 mv
LINK
https://www.dropbox.com/s/b6fw2avj4m8zx8k/cm-10.1-20130404-UNOFFICIAL-p760GPUOCUVver2.zip
BUGS:
1. All CM 10.1 bugs for p760
LATEST LINK
https://www.dropbox.com/s/qirfmvbnhvj28dg/cm-10.1-20130402-UNOFFICIAL-p760.zip
Instructions:
1. Download ROM and put to SD card
2. Enter recovery and Wipe/Factory Reset
3. Install ROM
Just to let you know, without clemsyn's help, I would not be able to get this thing to boot and work, because of him we have a fully working CM 10.1 in our device You might want to drop by and say thanks to him or probably donate for his help.
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
assassinanex said:
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
Click to expand...
Click to collapse
Dropbox download link works.
pinoyto: Thank You for doing this work. I tried building for the P769 a few weeks ago and I could never get it to boot. Good Job!!!
Here is a patch for another device having axis issues. maybe it will help:
http://review.cyanogenmod.org/#/c/24149/2/arch/arm/mach-msm/board-tenderloin.c
Some build.prop tweaks for inverted acellerometer:
http://androtab.info/cyanogenmod/rockchip/
So just use the Recovery Installer for a locked bootloader to enter recovery
mike6696 said:
So just use the Recovery Installer for a locked bootloader to enter recovery
Click to expand...
Click to collapse
This rom will not work if you have locked bootloader.
Re: [ROM] Cyanogenmod 10.1 for P769
so the only bugs just axis issue? and the only way to unlock bootloader is upgrade to jb? can`t wait for fully workin cm10.1 . i never like skinned android.
Sent from my LG-P769 using Tapatalk 2
Lelus said:
This rom will not work if you have locked bootloader.
Click to expand...
Click to collapse
I know my bootloader is unlocked i was talking about to enter recovery but I got it. Now i cant enter recovery with the rom so cant i just use adb shell to install gapps
I'm stupid. This post was a sign of it but I deleted it so you wouldn't know.
rooting p769 10g
assassinanex said:
Im already rooted with cwm on p769 10g. I was reading on the link you provided and it looks like i would have to start over again which would be a pain in the ass plus the link to the kdz is dead on that page so i dunno what should i do?
Click to expand...
Click to collapse
hello friend please could you post me a link to root the p76910g . thank you.
Re: [ROM] Cyanogenmod 10.1 for P769
Is this rom a good daily driver? If it is I might attempt to go through the trouble of unlocking the bootloader
Enviado desde mi LG-P769 usando Tapatalk 2
Juanito216 said:
Is this rom a good daily driver? If it is I might attempt to go through the trouble of unlocking the bootloader
Enviado desde mi LG-P769 usando Tapatalk 2
Click to expand...
Click to collapse
To early to tell since it was just released today.
This reeks of an April Fools joke. If it is, it's not funny. Hope it's not....
SovereignKnight said:
This reeks of an April Fools joke. If it is, it's not funny. Hope it's not....
Click to expand...
Click to collapse
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
psychoace said:
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
Click to expand...
Click to collapse
Glad to hear its not a joke. I think ill wait till this has all the kinks worked out. Good news, none the less.
Uh with all the different phones variations this has become a little difficult to do unless you include some semi-thorough instructions on how to install each rom. Right now it looks like after I unlocked my bootloader I should of flashed and rooted the V20 Europe rom with an edited hex bin. I shouldn't have flashed to a v10g rom like I did because the .bin is not hex edited correctly for Jelly Bean. This is my assumption. Am I right or wrong?
Re: [ROM] Cyanogenmod 10.1 for P769
Awesome. I cant wait for a stable release.
Sent from my LG-P769 using xda premium
psychoace said:
I just got finished installing it (took me awhile because I didn't have my bootloader unlocked and also couldn't figure out some things). It runs is all I can say because I haven't done anything with it yet. I'm right now looking for Google Apps then I will finish up my install. It still looks like mirrored screen is still an issue that get fixed once you lock and unlock your phone. Otherwise it's not an April Fools joke.
It seems I have lost CWM recovery mode. I tried installing it with the recovery app but when I reboot from the app I get a boot loop at the LG logo. I then shut down and boot up and am able to get back into CM10. I then try the Volume up+home key+power button method and it brings me to stock LG recovery. The app says that CWM is installed but it still seems LG recovery is the only thing there.
Click to expand...
Click to collapse
Thanks for this, it seems like the mounting points of recovery for p760 and p769 is different so I will have to change the recovery mount points too. I flashed my recovery via fastboot but you can flash recovery via Terminal.
https://www.dropbox.com/s/i575nvqeysj0ev8/recovery.img
move your recovery.img to /sdcard
Open Terminal
Type su
type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Then turn off..
Then Volume down+home key + Power button.
Update:
Lelus just informed me that there might be an easier process of unlocking the bootloader by using u-boot. There is no way for us to test it since we are already unlocked so whoever hasn't unlocked and want to try it out, contact Lelus.
Re: [ROM] Cyanogenmod 10.1 for P769
Nevermind
Sent from my LG-P760 using xda app-developers app
pinoyto said:
Thanks for this, it seems like the mounting points of recovery for p760 and p769 is different so I will have to change the recovery mount points too. I flashed my recovery via fastboot but you can flash recovery via Terminal.
https://www.dropbox.com/s/i575nvqeysj0ev8/recovery.img
move your recovery.img to /sdcard
Open Terminal
Type su
type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Then turn off..
Then Volume down+home key + Power button.
Update:
Lelus just informed me that there might be an easier process of unlocking the bootloader by using u-boot. There is no way for us to test it since we are already unlocked so whoever hasn't unlocked and want to try it out, contact Lelus.
Click to expand...
Click to collapse
Sweet, I almost thought I lost my phone there for a second. Well it would still be usable and I can push Google Apps with adb but I didn't know if I could tether flash ever again. Thanks, I am going to try this now.
psychoace said:
Sweet, I almost thought I lost my phone there for a second. Well it would still be usable and I can push Google Apps with adb but I didn't know if I could tether flash ever again. Thanks, I am going to try this now.
Click to expand...
Click to collapse
I think I know the issue... our sensors.omap4.so is looking for a different directory to enable sensor commands and unfortunately this folder is different from the p760... we will see how it goes... I'll try to move some directory around and fix permissions.
A good day to all!
I have had an issue with my S6 edge (SM-G925F, Philippines Globe Carrier Version) for months now wherein it keeps restarting/crashing. The problem persists so randomly, sometimes multiple times a day or sometimes a day or two without it. I've already tried everything I could find in the internet, such as; deleting the cache in recovery, factory wiping the phone, and flashing the newest firmware i found for it on sammobile. Noting seemed to work. This is my last attempt in fixing the phone before I give up. I hope someone can give me good advice about this.
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
yh man,same problem...i cant even boot to the system..is your led flashing blue?
buzzsaw345 said:
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
Click to expand...
Click to collapse
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
pexluka said:
yh man,same problem...i cant even boot to the system..is your led flashing blue?
Click to expand...
Click to collapse
Mine can actually boot to the system but it always crashes after some time of use.
callumbr1 said:
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
Click to expand...
Click to collapse
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
buzzsaw345 said:
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
Click to expand...
Click to collapse
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
callumbr1 said:
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
Click to expand...
Click to collapse
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
buzzsaw345 said:
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
Click to expand...
Click to collapse
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
callumbr1 said:
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
Click to expand...
Click to collapse
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
buzzsaw345 said:
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
Click to expand...
Click to collapse
No problem buddy enjoy your one plus 3
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
pexluka said:
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
Click to expand...
Click to collapse
Wouldn't say it was motherboard yet. After you flash your rom you need to boot to recovery and wipe data/cache. This will fix the apps crashing
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
pexluka said:
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
Click to expand...
Click to collapse
Do not pay for it. Chances are if you can't fix it they can't either.
So have you tried flashing stock firmware?
What Android version do you have and what region? What's full model number g925?
Reduce the cpu frequencies to 1200-800mhz for big and little and userspace governor. This the only fix.
ok,so one more thing,on the glass back of the phone sits one imei that is not correct,and on the battery is another,which reports 64g version,while next to that number is printed 32gb and phone actually has 32gb lool
it is supposed to be g925f,but after i installed some custom rom,pc showed it as g925s? i think it is due to rom signing the wrong model number
the last thing i have done was yesterday,and it was flashing firmware through kies again.
and this is what i get :
s6 edge powered by android,followed by blue screen 'installing system update',and then recovery
in the recovery,i get this :
android recovery
samsung/zeroltexx/zerolte
7.0/NRD90M/G925FXXU5EQBG
user/release-keys
*recovery options*
No suppoer SINGLE-SKU
Supported API: 3
dm-verity error...
i realy dont know what else to try,and i am open to all suggestions..i have read that emmc storage is broken so this kind of problems can occur,so maybe service would do that?
thank you,i know this is confusing and boring problem
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
pexluka said:
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/VOD/download/G925FXXU5EQBG/125195/
Download and flash that firmwsre through odin before you try anything else. Let me know what happens.
I can tell you it's likely not emmc failure. For this you would get random reboots and it would reboot to download mode. There you would have an error emmc_write_error.
wowo thanks,i just gave up on that phone,i will try again,i will report back!
just one question,why vodafone?
oh,and i did have random reboots on android m,but it would reboot to optimizing android and boot