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.
Related
Based off of htc-kernel-espresso repository from CyanogenMod github and a modified version of toastcfh's overclock patch.
espresso source based is for
espresso devices only
legend source based is for
espresso, legend, or aria devices
No support will be given, use at your own risk, DON'T FLASH unless you know what you are doing .
Version 3.5:
updated source to include interactive governor
added darchstar's patch to fix idle status being set NULL
added a 787 for those that can't do 806
incorporated changes into legend code base
http://www.mediafire.com/?9ziqlmh6vy26x
V4.0: (Requires setting scaling_max_freq in order to boot)
all frequencies included in one kernel.
added 480 back.
864 max
available frequencies: 245760, 400000, 480000, 600000, 768000, 787200, 806400, 825600, 844800, 864000
NOTE:
Since all frequencies are now playing nicely together, I am only going to be releasing one kernel version per source base.
It is up to you to set your maximum speed in your init.d files or you might not boot (since the maximum is 864).
For Those of you who have used my G1 kernels, this will not be an issue since you should know how to do it. For the others, good luck .
Essentially, you need to put something like...
Code:
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
somewhere in your init.d files. Personally I like to use 00banner since it's first to execute on cyanogenmod.
Don't forget that if you swap out an init.d file you need to make the new one executable. For example...
Code:
chmod 0750 /system/etc/init.d/00banner
http://www.mediafire.com/?7jyeovzuo8lx9
archive:
http://www.mediafire.com/?v6cdcjyf04ebd
These are koush's anykernel.zip's that change your boot and system images. To return to your original state just do a nandroid advanced restore of the boot and system partitions (of course you have to of backed them up first).
github (master branch is legend base, oc-espresso-2.6.29 branch is espresso base. Default is set to espresso)
sweet, he's doing an overclock kernel?? thats awesome!
posted a v2 to fix a problem with minimum frequency.
This version is set to 691/691 when screen is on and 245/245 when screen is off.
edit: this broke it.
dumfuq said:
posted a v2 to fix a problem with minimum frequency.
This version is set to 691/691 when screen is on and 245/245 when screen is off.
edit: this broke it.
Click to expand...
Click to collapse
Lol I was gonna post to not try and set it to a performance profile as it breaks the overclock.
Great work though I'm finally so glad to see this. I flashed it and boot was quite a bit faster as well. A 91mhz gain seemed to make quite a difference. If this arm cpu will hit 800 then this phones gonna fly.
Ok noticing some lag here and there. I just did a quadrant bench and only scored 333. I have not did a reboot since I flashed it. Will try and report back.
Sent from my T-Mobile myTouch 3G Slide using XDA App
v3. fixed for the night.
screen on 480/691
screen off 245/480
sultan.of.swing said:
Lol I was gonna post to not try and set it to a performance profile as it breaks the overclock.
Great work though I'm finally so glad to see this. I flashed it and boot was quite a bit faster as well. A 91mhz gain seemed to make quite a difference. If this arm cpu will hit 800 then this phones gonna fly.
Ok noticing some lag here and there. I just did a quadrant bench and only scored 333. I have not did a reboot since I flashed it. Will try and report back.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
was the lag on v1? if so the minimum frequency was dropping to 19mhz, that's why i had to do the next one.
never tried quadrant before...i kinda like
on test 1, i exerienced a TON of lag... i set min / max at 691 and got lag like a mofo >.> hopefully t3 doesnt lag so bad this time
quick question... if i do this kernel, and i dont like it, can i go back to the old one just by flashing the old one or would that break something??
you could easily make a backup boot image zip
thomas.nelson4 said:
quick question... if i do this kernel, and i dont like it, can i go back to the old one just by flashing the old one or would that break something??
Click to expand...
Click to collapse
This kernel is just for testing purposes. You don't want it for daily use. If you are not comfortable flashing random broken things, don't even bother with it. Currently it takes a big performance hit for 3d graphics and has no wifi.
dumfuq said:
This is a test, this is ONLY a TEST.
Based off of htc-kernel-espresso repository from CyanogenMod github
Wifi is broken.
Performance is LOCKED at 691 mhz.
This is an update.zip that replaces your boot.img. To return to the stock boot.img just do a nandroid advanced restore of the boot partition (of course you have to of backed it up first).
No support will be given, use at your own risk, DON'T FLASH unless you know what you are doing .
oc691-kernel-test-v1-signed.zip
oc691-kernel-test-v3-signed.zip
Click to expand...
Click to collapse
hey do you have the patch for this?
wesgarner said:
hey do you have the patch for this?
Click to expand...
Click to collapse
here is the diff
slide_oc.diff
fyi I ended up hardcoding the 691 instead of using the old technique because the divisor was giving me issues with anything over 652 and I was just trying to do a proof of concept anyway.
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Dumfuq, I love you.
Oakley44 said:
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Click to expand...
Click to collapse
guess what, ive got a GREAT answer for ya... that boot image is ONLY FOR froyo roms at this point. sorry bud :/
Oakley44 said:
Any reason it might go to black on boot-up...for minutes? Confict with new radio maybe?
My slide's looking very brickalicious at the moment so I'm gonna volume down and power into recovery; Just not booting. Was running Slidemeroot5r1.
Click to expand...
Click to collapse
Is SlideMeRoot5r1 a CyanogenMod-6.0.0? I think not.
dumfuq said:
Is SlideMeRoot5r1 a CyanogenMod-6.0.0? I think not.
Click to expand...
Click to collapse
Ahh, what douchey lord of noobs I am.
Ok well, needless to say I did a full restore and rebooted. Still goes to black. Any change you have a zip for the stock kernel?
breaks WIFI on SuperFly 1.2 ... me only???
dumb... i can't read
UM BUT maybe pushing some wlan.ko file....?
Oakley44 said:
Ahh, what douchey lord of noobs I am.
Ok well, needless to say I did a full restore and rebooted. Still goes to black. Any change you have a zip for the stock kernel?
Click to expand...
Click to collapse
just flash Slidemeroot5r1 rom without wipe and reboot
Sxyman815 said:
just flash Slidemeroot5r1 rom without wipe and reboot
Click to expand...
Click to collapse
Already wiped system/cache to go back to last restore. In the middle of restore as I type this... . Next time I'll read the thread title a bit better..........ok, yeah it worked .
Hi Guys,
Finally i can show you guys my knowledge where i'm realy strong in. C programming
I started this project to gain a good and stable kernel thats is support many roms. I'll hope some other devs want to join me in on this project to create together one good kernel instead of many splintered releases of the kernel. (At the end we only need 1 kernel right?)
Main project goals:
2.3.5 compatible (Sound problem etc)
MIUI and AOSP/CyanogenMod compatible
Tweaked to the bone
two way call record (2WCR)
You name it
What i already done:
OC to 1.5ghz
Fixed codec problem for 2.3.5 Roms
Added SmartassV2 governor
Snapdragon optimisations
If you want to help me in this project give em a pm and i hook you up to the proejct page
http://code.google.com/p/crypt0kernel/ commiting the init code takes longer then i expected...
Flash method for S-On users:
Follow this how-to:http://forum.xda-developers.com/show...59&postcount=2
And use this to copy the libs:
1. unpack downloaded ZIP file (for example to d:/temp)
2. connect device with computer with Android SDK tools (adb, fastboot)
3. reboot to bootloader
adb reboot bootloader
4. flash new kernel
fastboot flash zimage d:/temp/zImage
5. restart device
fastboot reboot
6. push new wifi module
adb push *.ko /data/local/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p22 /system
busybox cp /data/local/*.ko /system/lib/modules/
Click to expand...
Click to collapse
Ps. Zip files are CWM zip files so can be flashed by ClockwordMod
Great man, looking forward to have 3.5 sense working on our devices..with sound
keep up the good work
Regards
excellent! always good to have a new kernel do you think 1080p 2D video recording can be solved in kernel level?
Flashing it !
Good news!
If possible, also add support 2WCR (2-way call records)
will this work with s-on? and will it effect the dual core
and yet, this kernel on Root stock firmware can be put?
Gamburger said:
and yet, this kernel on Root stock firmware can be put?
Click to expand...
Click to collapse
I dont see the problem why not. Try it and make sure you do a backup before flashing.
crypt0night said:
I dont see the problem why not. Try it and make sure you do a backup before flashing.
Click to expand...
Click to collapse
hey man
would you pleased post this link:http://forum.xda-developers.com/showpost.php?p=18416359&postcount=2
to the first post incase S-on user like me need the alternative way to flash?
and this link for wifi issue
from: http://forum.xda-developers.com/showthread.php?t=1311812
How to install
1. unpack downloaded ZIP file (for example to d:/temp)
2. connect device with computer with Android SDK tools (adb, fastboot)
3. reboot to bootloader
adb reboot bootloader
4. flash new kernel
fastboot flash zimage d:/temp/zImage
5. restart device
fastboot reboot
6. push new wifi module
adb push *.ko /data/local/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p22 /system
busybox cp /data/local/*.ko /system/lib/modules/
Should we trust quadrant score on these? It seems setcpu doesn't want to play nice with leedroids ROM or these new kernals haha
Sent from my HTC EVO 3D X515m using XDA App
DJGurth said:
Should we trust quadrant score on these? It seems setcpu doesn't want to play nice with leedroids ROM or these new kernals haha
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
dun use setcpu as only mod 1st core as they said before. i didnt try it. use cpumaster or system tuner to oc
can't flash it:
assert failed:write_raw_image("/tmp/newboot.img", "boot")
error in /sdcard/Cript0kernel.zip
(Status 7)
Installation aborted
im using cript0 rom 1.2
hboot 1.49.0011 s-on
steveruthless said:
can't flash it:
assert failed:write_raw_image("/tmp/newboot.img", "boot")
error in /sdcard/Cript0kernel.zip
(Status 7)
Installation aborted
im using cript0 rom 1.2
hboot 1.49.0011 s-on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1049102
or try android control to flash zimage
i m in 149.0013 s-on
crypt0night said:
I dont see the problem why not. Try it and make sure you do a backup before flashing.
Click to expand...
Click to collapse
Just earlier tried to put the Kernel UNITY V1 beta - did not, an error .... (Status 7)
Installation aborted. Even wi-fi stopped working. Well that did backup)
Сame back.
Gamburger said:
Just earlier tried to put the Kernel UNITY V1 beta - did not, an error .... (Status 7)
Installation aborted. Even wi-fi stopped working. Well that did backup)
Сame back.
Click to expand...
Click to collapse
same problem here..unable to flash using cwm when still s-on..will try different method.
Installed through CWM no problem for me, just waiting for Villain ROM to boot.
Looking forward to Smartass govenor2
Thanks for this Crypt0night, it is great to now see some movement from great devs now we have the source code.
keep it up buddy your work is much appreciated.
Edit:
Seems to be working well, Wifi Ok, governor set, Oc'ed to 1536 with CPU Master
Is it possible to implement a zero shutter lag code?
Would be really nice! :-D
And may be two versions with and without two way recording because i read that it can drain the battery bad sometimes..
Sent from my HTC EVO 3D X515m using Tapatalk
ilovemeow said:
http://forum.xda-developers.com/showthread.php?t=1049102
or try android control to flash zimage
i m in 149.0013 s-on
Click to expand...
Click to collapse
successfully flash using this but system tuner still show the highest oc is 1118 mhz
steveruthless said:
same problem here..unable to flash using cwm when still s-on..will try different method.
Click to expand...
Click to collapse
the fact of the matter is there is a root and s-off. Only rom - stock.
osrix said:
Installed through CWM no problem for me, just waiting for Villain ROM to boot.
Looking forward to Smartass govenor2
Thanks for this Crypt0night, it is great to now see some movement from great devs now we have the source code.
keep it up buddy your work is much appreciated.
Edit:
Seems to be working well, Wifi Ok, governor set, Oc'ed to 1536 with CPU Master
Click to expand...
Click to collapse
Are you s-on or s-off mate ?
I don't think anyone that is s-off is having issues with any of the new kernel's. It's just us with s-on using the htc unlock method that we can't OC. Installing via recovery works with no errors, but still no option to OC as default values only avail..
Cheers
Unlocking the bootloader on p769 is DIFFICULT, the most difficult part is working with the touch screen which is wonky during this process. I highly suggest that we wait for LG's latest Jelly Bean for p769 instead of doing this, but if you are wanting to experiment like me, then read on.
Please note that every boot will ALWAYS have a mirrored image after doing this procedure.
First and foremost, thanks to Lelus for helping me through the process. Second, you need to be very familiar in flashing KDZ offline with this procedure (thanks cmahendra)
http://forum.xda-developers.com/sho....xda-developers.com/showthread.php?p=36351786
1. Download this link to get p760 20B Europe open and flash it on p769 using the KDZ offline method.
http://csmgdl.lgmobile.com/swdata/WDLSW/LGP760/ANEUWH/V20b_00/V20B_00.kdz
2. After flashing you will notice you have two issues...Mirrored Image and Wonky touch screen. Mirrored image can be easily remedied by using a mirror to read the screen better. The Touch screen issue is the most difficult because after flashing 20B, we need to enable USB debugging in developer options. (thanks cmahendra)
Wonky Touchscreen:
This is how I got through the wonky touchscreen. Imagine putting a line in the middle of the screen crosswise (or like dividing the screen crosswise), you have to top screen and bottom screen. The Imaginary line would be the bottom of the top screen and the BOTTOM of the bottom screen (like the bottom screen's bottom is in the middle of the screen and the top of the bottom screen is in the bottom of the whole screen). It takes some practice but you will get it.
Make sure you face a mirror with your phone to get around the mirror imaged.
3. OK, now you have to go to Settings --> Developer Options ---> and tick USB debugging (You can also tick "Show touches" to make it easier).
4. LET YOUR PHONE STAY ON FOR 30 minutes or more (Very Important or you won't be able to unlock your bootloader). Then connect your device to PC and type "adb devices" and make sure your p769 is seen by the computer. Then type "adb reboot oem-unlock" This will reboot your device and send you to a "mirrored" confirmation screen. Basically just press Volume UP button to confirm unlock... then it will send you to fastboot, you can just press the power button for 10 seconds and reboot.
5. After rebooting, you need to flash 10G kdz back, in my experience, the offline flashing method by booting to SW mode did not work... It hanged up at 15% and said my device is not connected to USB. The only way for me to flash 10G KDZ back was to boot in JB (mirrored) and then instead of Emergency Mode, I used DIAG mode while the device is connected to PC. Only then was I able to flash back to 10G.
6. After flashing 10G KDZ, you won't be able to boot. Turn it off and do a hard reset (Power button + Volume UP + Menu Button).
7. Upon reboot from 10g, you will still have the mirrored image, but if you press the power button and turn it back on, the mirrored image will be fixed. Then comes the wonky touch screen. Beside from having the wonky touch screen you will notice that the whole left and right side is also inverted which makes it very difficult but doable with practice.
8. In 10G, we need to enable USB debugging again, then root the device with this procedure
http://forum.xda-developers.com/showthread.php?t=2171243
(Remember to use DIAG mode in reflashing 10G for the second time in rooting the device)
9. After rooting the device, we need to fix the touchscreen with this (Post #24)
http://forum.xda-developers.com/showthread.php?t=2182867&page=3
and go to post #24..
That's it AGAIN, I highly suggest we wait for JB for our devices instead of this.
If ever you want to overclock your GPU at 384, here is a link to do that..
https://www.dropbox.com/s/ofuijfgx4e694gl/bootoc.img
Goodluck
Awsome
I'd add ,disable your lock screen before flashing jb
Awesome work :victory:
By the way, you might want to bold the warnings involved with this process so that it stands out better. I have a feeling some people won't read the entire post and dive in without knowing exactly what they are getting into
I have successfully overclocked our GPU to 384 Nenamark 2 scores from 32.7 jumped to 36.9 Do we have a working CWM with our proper mount points?
I also noticed the OC'd the GPU at 384, I cannot OC the cpu to 1200 via kernel.
Awesome work!
I completely agree with waiting on an official update to JB.. I personally don't see much of a point in unlocking until we can boot into a custom ROM.
I've given up on this device - but with a hopeful update to JB and a hopeful official unlocking method on the horizon I may hold on.
Sent from my LG-P769 using xda app-developers app
I have installed CWM with no issues (aside from mirrored image) and doing backup at the moment. Might try CWM.
Looks like I can Overclock the CPU to 1.2ghz with the OC script and keep the GPU at 384 This thing is getting faster
I just unlocked mine,
Lelus said:
I just unlocked mine,
Click to expand...
Click to collapse
LMK if you want the boot.img with the OC'd GPU
Were you able enter fast boot after you restored 10g ?
yes, using omap4boot
Mine is now unlocked too. Back on 11a with fixed touchscreen. You weren't kidding about the touch being tricky. Took me longer to get into developer options than any other step I took the recovery.img from the jellybean root/recovery thread and flashed it in fastboot and now have working recovery too. It's mirrored like you said but it's easy enough to navigate like that. Restored data from the backup I made before starting, it's like nothing happened.
Sent from my LG-P769 using xda premium
Tablechair said:
Mine is now unlocked too. Back on 11a with fixed touchscreen. You weren't kidding about the touch being tricky. Took me longer to get into developer options than any other step I took the recovery.img from the jellybean root/recovery thread and flashed it in fastboot and now have working recovery too. It's mirrored like you said but it's easy enough to navigate like that. Restored data from the backup I made before starting, it's like nothing happened.
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
Great, LMK if you are interested with the overclocked GPU kernel at 384
BTW, if we need to flash via SW update, looks like we need the original u-boot.img and x-loader.img and enter fastboot via omap4boot. I mean this this is totally unbrickable
Tablechair said:
Mine is now unlocked too. Back on 11a with fixed touchscreen. You weren't kidding about the touch being tricky. Took me longer to get into developer options than any other step I took the recovery.img from the jellybean root/recovery thread and flashed it in fastboot and now have working recovery too. It's mirrored like you said but it's easy enough to navigate like that. Restored data from the backup I made before starting, it's like nothing happened.
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
Awesome!
Now any chance we can get cm/aokp or even better - PACman ROM booted on our 769?
Sent from my LG-P769 using xda app-developers app
I have flashed the original x-loader in my unlocked device and it seems OK so it is definitely the p769 u-boot that is locked. I also noticed that the screen is still mirrored at boot and I believe this is due to the screen size differences of the p760 and I we can find a way to fix the screen size in u-boot, then we will get the mirror image fixed.
pinoyto said:
I have flashed the original x-loader in my unlocked device and it seems OK so it is definitely the p769 u-boot that is locked. I also noticed that the screen is still mirrored at boot and I believe this is due to the screen size differences of the p760 and I we can find a way to fix the screen size in u-boot, then we will get the mirror image fixed.
Click to expand...
Click to collapse
strange, after I flashed stock xloader and uboot my screen is no longer mirrored and colors are normal at boot
Lelus said:
strange, after I flashed stock xloader and uboot my screen is no longer mirrored and colors are normal at boot
Click to expand...
Click to collapse
hmm..I remember getting a security error after flashing both..maybe we flash xloader first then uboot? or maybe send your xloader and uboot to me to try? Thanks.
pinoyto said:
hmm..I remember getting a security error after flashing both..maybe we flash xloader first then uboot? or maybe send your xloader and uboot to me to try? Thanks.
Click to expand...
Click to collapse
Yes I flashed x first but it might not matter
I'd advise anyone to be very, very careful about flashing xloader and uboot.
Lelus said:
Yes I flashed x first but it might not matter
I'd advise anyone to be very, very careful about flashing xloader and uboot.
Click to expand...
Click to collapse
Thanks, so no security error? I'll try it.
Update... I still get security error Any tips?
pinoyto said:
Thanks, so no security error? I'll try it.
Click to expand...
Click to collapse
no security error, everything is back to normal except for some reason my phone won't enter fastboot no matter what,but it was like that before I flashed v20
---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------
pinoyto said:
Thanks, so no security error? I'll try it.
Update... I still get security error Any tips?
Click to expand...
Click to collapse
Do you have CWM recovery , or custom kernel ?
What if you restore to stock 10g ?
Lelus said:
no security error, everything is back to normal except for some reason my phone won't enter fastboot no matter what,but it was like that before I flashed v20
---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------
Do you have CWM recovery , or custom kernel ?
What if you restore to stock 10g ?
Click to expand...
Click to collapse
I have a custom kernel.. that is why... the u-boot from original won't allow custom kernels. I'd stay with my u-boot then since it lets me OC the GPU.
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 16 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
flo (Nexus 2013 Wi-Fi): CF-Auto-Root-flo-razor-nexus7.zip
deb (Nexus 2013 LTE): CF-Auto-Root-deb-razorg-nexus7.zip
Very happy to see you here too. Thx for your work.
Sent from my Nexus 7 using xda premium
Chainfire said:
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
Click to expand...
Click to collapse
For Flo, bootloader is volume down and power.
Newbie question - Once rooted with this method will I still get OTA updates? If so will it retain root?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
User_99 said:
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
Click to expand...
Click to collapse
Thats not true... I got the 4.3.1 update for my deb and had root+twrp. After hit install it boot to twrp and installs the ota after boot up root is still there. No Problems here
Great that it works fine for you!
But that will work not for all customers. Some reported that after they recived and downloaded the OTA they got an error while installation in custom recovery.
I rooted my Nexus 7c LTE..
now i can see an unlock logo in startup... anywhere i can remove it?
thanks!
No, that's normal for unlocked bootloader. Only not shown when you close the bootloader again.
Thank you!
any idea how to close the bootloader?
http://www.wugfresh.com/nrt/
Nexus Toolkit - easy way to lock the bootloader. But, for Root, you need an Unlock Bootloader...
decide...
THANKS!!!
is the auto-root still working on new kit-kat update?
ritz_cal78 said:
is the auto-root still working on new kit-kat update?
Click to expand...
Click to collapse
Nope. Already tired twice.
so if i want to install TWRP recovery, i have to flash it after i install CF-auto root?
how do i get to the steps u mentioned using mac?
xdviper said:
Nope. Already tired twice.
Click to expand...
Click to collapse
It worked perfectly for me first try. I should say that I had just rooted my Nexus 7 LTE with Chainfire's method before I updated my N7 OTA. After the update, root was lost. I simply went through the steps again and re-rooted it. I should also state that I did not lose any of my data on during the 2nd root.
I'm going to donate to Chainfire.
same here, only difference,
I came from a factory image fash. Auto root worked
Send from the N7²
Will this work a stock n7 2 running KK?
xbs said:
Will this work a stock n7 2 running KK?
Click to expand...
Click to collapse
Worked OK for me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Well i used to have a hox+ with Android Revolution custom rom and a custom kernel. I tried to power it up but it stucks at htc logo,then reboots and goes straight to twrp recovery. I tried to flash again the rom via adb but i can't see my device in cmd. I found and dowloaed htc drivers my htc,plus adk and htc sync manager but still no luck..any ideas what is going on here?
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
i360droid said:
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
Click to expand...
Click to collapse
fastboot is not recognised etc...........any ideas?
smavr said:
fastboot is not recognised etc...........any ideas?
Click to expand...
Click to collapse
ok, add me on skype, i360faceplant, i will walk you through it step by step
i360droid said:
ok, add me on skype, i360faceplant, i will walk you through it step by step
Click to expand...
Click to collapse
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
smavr said:
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
Click to expand...
Click to collapse
what was up with it?
i360droid said:
what was up with it?
Click to expand...
Click to collapse
Well, i just made a mistake at adb sideload...
smavr said:
Well, i just made a mistake at adb sideload...
Click to expand...
Click to collapse
lol
i360droid said:
lol
Click to expand...
Click to collapse
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
ahighfield said:
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Click to expand...
Click to collapse
to get into bootloader, hold down the vol down and power, the home lights will flash (atleast they do when its booting), it will reboot, when you get the htc logo, let go of power button. and now try a stable er version of the rom.
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
ahighfield said:
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
Click to expand...
Click to collapse
ok, dont do an ota update in cm, you need s-off, which you cant get on the hox+
flash the rom, flash the boot image, boot, reboot into recovery, SIDELOAD gapps and that should work. use cm10 for the moment, as cm11 has an annoying system ui crash loop bug.
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
ahighfield said:
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The phone will boot loop, as the kernal is different to the rom