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 .
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?
Can I flash mods, kernels or boot images over CleanRom ICSE 2.3? I've tried flashing a custom kernel (in an attempt to further speed up my phone) but it almost completely bricked my phone. I am fearing the potential paperwight from flashing anything else over this rom. Any advice?
Thanks!
I know for a fact changing boot animations won't hurt. Using CleanROM 2.3 and the Dice animation from WasabiWa83's thread.
joey2164 said:
I know for a fact changing boot animations won't hurt CleanROM 2.3 and the Dice animation from WasabiWa83's thread.
Click to expand...
Click to collapse
I've noticed that changing it manually through a root explorer (Replacing original boot img. with the renamed custom img.) doesn't work the same way. I don't see the same files in the system's media folder.
The instructions in that thread worked for me, but you have to follow them stringently. I use a windows computer, and somehow windows changed the state of the zip folder I was flashing to my phone, causing it to skip the animation. Downloading 7zip and ensuring the zip is formatted as "store" rather than compressed worked immediately.
joey2164 said:
The instructions in that thread worked for me, but you have to follow them stringently. I use a windows computer, and somehow windows changed the state of the zip folder I was flashing to my phone, causing it to skip the animation. Downloading 7zip and ensuring the zip is formatted as "store" rather than compressed worked immediately.
Click to expand...
Click to collapse
I tried what the thread said, followed the instructions perfectly, but now when I boot up, my phone doesn't even have its boot image. Crap
I'm running the one custom kernel for ICS with cleanROM 2.3 ics. So yes you can. Otherwise, what else is out there?
ο χάκερ said:
I tried what the thread said, followed the instructions perfectly, but now when I boot up, my phone doesn't even have its boot image. Crap
Click to expand...
Click to collapse
New download links are going up in a few minutes. They should (hopefully) all be fixed now to work on all ROMs. There were issues with the way the folders were in the Zips. Thanks to Rom-Addict, we should have them working now. If you try one in a minute and it works, make sure you find a post by Rom-Addict and thank him. That was a lot of work to get those going like that.
nrfitchett4 said:
I'm running the one custom kernel for ICS with cleanROM 2.3 ics. So yes you can. Otherwise, what else is out there?
Click to expand...
Click to collapse
There was an overclocked kernel for a different rom that overclocked to 1.8 Ghz. I don't remember where I got it or what it came from. I'll look around when I get home from school.
Now that the new hboot doesn't allow S-ON devices to flash kernels I went ahead and adapted this for the LTE. It's something I started for the Evo 3D back in January, but when a new way to get S-OFF was found I sat it aside and had forgotten about it.
When used it tries to flash the kernel like normal and doesn't do anything special if able to, otherwise it will copy a script to the system partition and install the kernel when the ROM tries to boot up. All that's needed is for a few lines to be added to the updater-script and it can do the rest.
I'll update this with more information at a later time, but for now I just want to say thank you to everyone who has helped contribute ideas and tested. As always, any help with improving it is welcomed.
How To Use It
This is mainly for ROM and kernel devs to use before releasing, but it can easily be added to any that don't normally use it. For more detailed instructions see Page 3.
Download and add the "kernel" folder to your update zip
Edit your updater-script and use the following when you are ready to install the boot.img
Code:
ui_print("Installing Kernel, please wait...");
package_extract_file("boot.img", "/tmp/boot.img");
package_extract_dir("kernel", "/tmp/kernel");
set_perm_recursive(0, 2000, 0777, 0777, "/tmp/kernel");
run_program("/tmp/kernel/install_kernel.sh", "/tmp/boot.img", "/tmp/bootready.tmp");;
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") != "READY",(
ifelse(file_getprop("/tmp/bootready.tmp","kernel.ready") == "STARTUP",
ui_print("Kernel Will Be Installed On Startup."),
ui_print("ERROR: Kernel Not Installed!")
)
));
Sign the zip and it can then be installed like normal from any device with a custom recovery
Changes
v0.57
flashboot.sh - Fixed the case statement that verifies the kernel flashed properly
flashboot.sh - Moved the call for DD to save the old kernel so that it always gets used
Downloads/Sources
Kernel Folder on DevHost (MD5: 27eB86aae3562e147d86b8dfe7a04786)
Google Code
Github - All files including the flashboot binary source
How Can I Test It With S-OFF?
If you comment out the dd command that writes the boot.img it will act like your device has S-ON.
Edit install_kernel.sh and change:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
to:
Code:
echo "-Trying to write the new boot.img and verify it's MD5"
#$BBDD if=$BOOTPADDED of=$BLOCKBOOT; sync
rm -f $BOOTOLD
Where Are The Log Files?
In the recovery it uses: /tmp/recovery.log
On boot it uses: /data/local/bootinfo.txt
What Does This Need To Work?
A custom recovery
A valid kernel already installed with init scripts to start either /system/bin/app_process or /system/bin/netd
What Recoveries Does It work With?
Most of my testing has been done with TWRP, but it should work just as well with any other recovery
Why Did My Phone Reboot Back To The Recovery?
If it is unable to flash the kernel it will leave the old one in place and reboot back to the recovery. If you are able to, please pull the log file from /data/local/bootinfo.txt and send it to me so I can see what needs to be fixed.
What If I Get A Bootloop?
Either the kernel you flashed doesn't work with your ROM or there was an error and it's unable to reboot back to the recovery. If you hold volume down it should bring up the bootloader, from there use the volume and power buttons to select 'Recovery'.
Why Does My Phone Boot Straight To The Bootloader?
You either managed to wipe your boot partition (kernel) or sometimes this will happen when upgrading hboots. If you are S-ON you will need to flash a new boot image from fastboot.
Reserved for later use
Cute
Does this work for AOSP based kernels as well?
-Cupper- said:
Cute
Click to expand...
Click to collapse
Thanks Cupper
sivarticus85 said:
Does this work for AOSP based kernels as well?
Click to expand...
Click to collapse
Yup, it's all the same to it. The only thing it needs to work is for some sort of kernel to already be installed.
good stuff!!!!!!!
Good stuff man. Like always, xhausx contributing genius stuff for all. Thanks. :thumbup:
Sent from my EVO using xda premium
Awesome. Thanks.
via eVo.
implimenting in my next installer
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
ca1ne said:
Would be a nice setup, aroma choose the way to install, boot.img or anykernel flash
Then you can flash the modules either way...
Thanks for the script. It will definitely get used.
Click to expand...
Click to collapse
Let me know if you need any help implementing it. I know the instructions aren't very detailed yet so I'll see about clarifying them some more here in a little bit.
Cool man
Sent from my EVO using xda premium
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
cgrimm9 said:
I don't mean to highjack anyone thread I was ready to do this since meanrom went with the evilz kernal. since I was s-on on the 1.15 boot. I was going to do this till I found a app on the market place called flash image gui which installed the kernal right on the phone.was simple and just plain easy no typeing anthing in just a click of a buttone.
Click to expand...
Click to collapse
Since the kernel is only writeable from the rom this does something similar, except it does it after you flash the rom and it's automatic.
You could look at it as the rom itself installs it's own kernel. That's one of the reasons why it may look so convoluted, but for a rom/kernel dev to actually implement it is easy once you know how it works.
JohnCorleone said:
I used Flash Image GUI on my NS4G all of the time. The last 2 updates were to add this phone and the Nexus 7. It takes about 10 seconds to flash a kernel or recovery img. Its a JoeyKrim app...so you know its legit. It actually saved me last night when testing a N7 kernel overclocked over 1.99. . The kernel somehow made my N7 not boot to recovery no matter what I tried so I stuck a different kernel in that app, flashed it and once it booted I flashed the CWM 6.0.1.0 and I was completely fixed. Money well spent.
Edit..XhausX, I bought my first 2 HTCs ever about 2 weeks ago. They are both s on 1.13 but I need to either return on to full stock or use your rooted stock. I need to help my mother out. She's using a Samsung Moment! Ouch.... I am downloading that now. Is it a simple wipe and flash? If its more difficult, I will gladly shoot a donation your way if you can help me. I think I prefer her to be rooted stock so your odex version is the call...should have mentioned I know squat about the HTC methods. Regaw_Leinard got me where I am now
Sent from my EVO using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If you no longer need it rooted personally I would get s-off first and then run the latest RUU to restore it to stock. That way you'll always be able to re-root anytime without hassle, but the device can still be completely stock and used normally.
Zarboz said:
implimenting in my next installer
Click to expand...
Click to collapse
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Evolutionmods said:
+1 on that, where do i add this in the updater and what do we do with Blk21 just leave it or will it work around it.
Click to expand...
Click to collapse
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
Captain_Throwback said:
Is it possible to get a mirror of the Dev-Host file? The 'drivers are currently being updated', and I wanted to try adding this to my stock 2.13.651.1 ROM so as to avoid the inevitable questions from noobs that are S-ON about why the ROM won't boot .
Click to expand...
Click to collapse
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
xHausx said:
Usually it's best to run it last so everything else is already in place. It will also check the recovery for the mount point, so that line won't be needed with it.
For your paranoid android rom you could use something like this: http://pastebin.com/rGVDKK2u
I'm not able to test it atm though so you'll probably want to verify it's good first.
mirror: https://dl.dropbox.com/u/18734200/kernel-installer-v0.56.zip
Click to expand...
Click to collapse
And of course the Dropbox link is now dead too .
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.
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.